Javax.resource.spi.ResourceAdapterInternalException: max connections reache

Hello,
I am writing an application to read messages from queues.
Everything seems to be working fine, but after a number of un-deployments and deployments I start getting the following exception and have no choice but to restart the application server.
Any hint on what the root cause might be?
Exception stack trace:
2008-02-15 14:47:19,095 WARN [org.jboss.system.ServiceController:424] Problem starting service jboss.j2ee:ear=Application-1.0.ear,jar=Application-1.0.jar,name=MDB,service=EJB3
org.jboss.deployment.DeploymentException: Endpoint activation failed ra=jboss.jca:service=RARDeployment,name='wmq.jmsra.rar' activationSpec=javax.jms.Queue:wsmq/Q@@localhost; - nested throwable: (javax.resource.spi.ResourceAdapterInternalException: max connections reached)
     at org.jboss.deployment.DeploymentException.rethrowAsDeploymentException(DeploymentException.java:53)
     at org.jboss.ejb3.mdb.inflow.JBossMessageEndpointFactory.activate(JBossMessageEndpointFactory.java:310)
     at org.jboss.ejb3.mdb.inflow.JBossMessageEndpointFactory.start(JBossMessageEndpointFactory.java:194)
     at org.jboss.ejb3.mdb.MessagingContainer.startProxies(MessagingContainer.java:190)
     at org.jboss.ejb3.mdb.MessagingContainer.start(MessagingContainer.java:156)
     at org.jboss.ejb3.mdb.MDB.start(MDB.java:126)
     at sun.reflect.GeneratedMethodAccessor90.invoke(Unknown Source)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:585)
     at org.jboss.ejb3.ServiceDelegateWrapper.startService(ServiceDelegateWrapper.java:103)
     at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289)
     at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245)
     at sun.reflect.GeneratedMethodAccessor5.invoke(Unknown Source)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:585)
     at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
     at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
     at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
     at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
     at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
     at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978)
     at $Proxy0.start(Unknown Source)
     at org.jboss.system.ServiceController.start(ServiceController.java:417)
     at org.jboss.system.ServiceController.start(ServiceController.java:435)
     at sun.reflect.GeneratedMethodAccessor10.invoke(Unknown Source)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:585)
     at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
     at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
     at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
     at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
     at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
     at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
     at $Proxy361.start(Unknown Source)
     at org.jboss.ejb3.JmxKernelAbstraction.install(JmxKernelAbstraction.java:120)
     at org.jboss.ejb3.Ejb3Deployment.registerEJBContainer(Ejb3Deployment.java:301)
     at org.jboss.ejb3.Ejb3Deployment.start(Ejb3Deployment.java:362)
     at org.jboss.ejb3.Ejb3Module.startService(Ejb3Module.java:91)
     at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289)
     at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245)
     at sun.reflect.GeneratedMethodAccessor5.invoke(Unknown Source)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:585)
     at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
     at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
     at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
     at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
     at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
     at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978)
     at $Proxy0.start(Unknown Source)
     at org.jboss.system.ServiceController.start(ServiceController.java:417)
     at sun.reflect.GeneratedMethodAccessor10.invoke(Unknown Source)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:585)
     at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
     at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
     at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
     at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
     at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
     at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
     at $Proxy34.start(Unknown Source)
     at org.jboss.ejb3.EJB3Deployer.start(EJB3Deployer.java:512)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:585)
     at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
     at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
     at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
     at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
     at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
     at org.jboss.mx.interceptor.DynamicInterceptor.invoke(DynamicInterceptor.java:97)
     at org.jboss.system.InterceptorServiceMBeanSupport.invokeNext(InterceptorServiceMBeanSupport.java:238)
     at org.jboss.wsf.container.jboss42.DeployerInterceptor.start(DeployerInterceptor.java:87)
     at org.jboss.deployment.SubDeployerInterceptorSupport$XMBeanInterceptor.start(SubDeployerInterceptorSupport.java:188)
     at org.jboss.deployment.SubDeployerInterceptor.invoke(SubDeployerInterceptor.java:95)
     at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
     at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
     at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
     at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
     at $Proxy35.start(Unknown Source)
     at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1025)
     at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1015)
     at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:819)
     at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782)
     at sun.reflect.GeneratedMethodAccessor21.invoke(Unknown Source)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:585)
     at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
     at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
     at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
     at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
     at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
     at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
     at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
     at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
     at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
     at $Proxy10.deploy(Unknown Source)
     at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanner.java:421)
     at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.java:634)
     at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.doScan(AbstractDeploymentScanner.java:263)
     at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.loop(AbstractDeploymentScanner.java:274)
     at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.run(AbstractDeploymentScanner.java:225)
Caused by: javax.resource.spi.ResourceAdapterInternalException: max connections reached
     at com.ibm.mq.connector.ResourceAdapterConnectionPool.allocateConnection(ResourceAdapterConnectionPool.java:231)
     at com.ibm.mq.connector.ResourceAdapterImpl.endpointActivation(ResourceAdapterImpl.java:333)
     at org.jboss.resource.deployment.RARDeployment.endpointActivation(RARDeployment.java:271)
     at org.jboss.resource.deployment.RARDeployment.internalInvoke(RARDeployment.java:226)
     at org.jboss.system.ServiceDynamicMBeanSupport.invoke(ServiceDynamicMBeanSupport.java:156)
     at org.jboss.mx.server.RawDynamicInvoker.invoke(RawDynamicInvoker.java:164)
     at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
     at org.jboss.ejb3.JmxClientKernelAbstraction.invoke(JmxClientKernelAbstraction.java:44)
     at org.jboss.ejb3.mdb.inflow.JBossMessageEndpointFactory.activate(JBossMessageEndpointFactory.java:305)
     ... 101 more
ObjectName: jboss.j2ee:ear=Application-1.0.ear,jar=Application-1.0.jar,name=MDB,service=EJB3
State: FAILED
Reason: org.jboss.deployment.DeploymentException: Endpoint activation failed ra=jboss.jca:service=RARDeployment,name='wmq.jmsra.rar' activationSpec=javax.jms.Queue:wsmq/Q@@localhost; - nested throwable: (javax.resource.spi.ResourceAdapterInternalException: max connections reached)My current configuration is:
- JBoss 4.2.2-GA (linux)
- WS MQ 6.0.2.2 (linux)
I have configured JBoss the following way:
- added wmq.jmsra.rar to the $JBOSS_SERVER/deploy directory
- added com.ibm.mqetclient.jar to the $JBOSS_SERVER/lib directory
- created $JBOSS_SERVER/deploy/wmq.jmsra-ds.xml as follows
<?xml version="1.0" encoding="UTF-8"?>
<connection-factories>

<mbean code="org.jboss.resource.deployment.AdminObject" name="jca.wmq:name=wsmqQ">
    <attribute name="JNDIName">wsmq/Q</attribute>
    <depends optional-attribute-name="RARName">jboss.jca:service=RARDeployment,name='wmq.jmsra.rar'</depends>
    <attribute name="Type">javax.jms.Queue</attribute>
    <attribute name="Properties">
      baseQueueManagerName=QM1
      baseQueueName=Q
    </attribute>
</mbean>

<tx-connection-factory>
    <jndi-name>MQCF</jndi-name>
    <xa-transaction />
    <rar-name>wmq.jmsra.rar</rar-name>
   <connection-definition>javax.jms.ConnectionFactory</connection-definition>
    <config-property name="channel" type="java.lang.String">SYSTEM.DEF.SVRCONN</config-property>
    <config-property name="hostName" type="java.lang.String">127.0.0.1</config-property>
    <config-property name="port" type="java.lang.String">1414</config-property>
    <config-property name="queueManager" type="java.lang.String">QM1</config-property>
    <config-property name="transportType" type="java.lang.String">CLIENT</config-property>
</tx-connection-factory>My java MDB (EJB3) is:
@MessageDriven(name = "MDB", activationConfig = {
        @ActivationConfigProperty(propertyName = "destination", propertyValue = "wsmq/Q"),
        @ActivationConfigProperty(propertyName = "destinationType", propertyValue = "javax.jms.Queue"),
        @ActivationConfigProperty(propertyName = "transportType", propertyValue = "CLIENT"),
        @ActivationConfigProperty(propertyName = "useJNDI", propertyValue = "true"),
        @ActivationConfigProperty(propertyName = "maxPoolDepth", propertyValue = "1") }, messageListenerInterface = MessageListener.class)
@ResourceAdapter("wmq.jmsra.rar")
public class MDB implements MessageListener {
    public void onMessage(Message message) {
        return;
}Thanks in advance for any information!
cheers!

hi
this is known to IBM as APAR IC54346 - fixed in pack 6.0.2.3

Similar Messages

ORA-00020 error, max connections reached

I tried logging into TOAD from back-end but it started giving error like 'ORA-00020, maximum no of connections exceeded...'. What, are the steps we can take to counter this.
I hope, my question is clear.
Please, help in solving the doubt.
regards

hi,
thanks, for your answer. But, in init.ora, the entries are like:-
# Processes and Sessions
#processes=250
processes=300
Is, there a difference from this in the maximum sessions possible which is given by 'sessions' parameter as
SQL> connect /as sysdba
SQL> show parameters sessions
When, I give :-
select count(1) from v$session
it gives 460.
Can, you please clear the doubts in the scenario put as above.
regards

Error in javax.resource.cci.Connection during Compilation

Hi,
I am using NW 04 to write a par for my EP.
But I encountered the following error at the line
package com.sap.nwrig.demo;
The error is as shown :
This compilation unit indirectly references the missing type javax.resource.cci.connection (typically some required class file is referencing a type outside the classpath)
Do hope anyone could help.
Thanks.
Regards,
Mike Lee

Hi Mike,
I guess you need to add the JCA library that contains the javax.resource.cci.Connection class to the classpath of your project. Here's how to do it (assuming you're using the NetWeaver Developer Studio):
1. Right click on your project and choose Properties.
2. Choose Java Build Path from the lefthand side tree, and then choose the Libraries tab on the right.
3. Click on the Add External JARs button and browse to the following directory: <NW_Dev_Studio_inst_dir>\eclipse\plugins\com.tssap.ext.libs.j2ee_1.3\lib
4. Select connector.jar and choose Open.
This adds the library and now the referenced type should be resolved.
Regards,
Ivo

LDAP "ServerListener" stops responding (Max number of connections reached)

Hi --
The last four work days, in the evening, our OAS 10G server stopped processing portal logon requests. The response to login requests was this message:
Internal error WWC-00006 Unexpected error
encountered in wwsec_app_priv.process)signon
(User-Defined Exception) (WWC-41417)
An exception was raised when accessing the
Oracle Internet Directory 81: Can't contact
LDAP server. Details:
Operation dbms_ldap.simple_bind_s (The message also included other details such as the host, port and DN, and a reference to error message WWC-41743.)
Suspecting an LDAP problem, we looked on the server, and in ORACLE_HOME/LDAP/LOG I found recent log files (oidldapd[instance]s[pid].log) with several megs of messages that look like this:
2005/06/17:17:59:33 * ServerListener :2 * ERROR :
ServerListener : Max numbers of connections reached.
Num Conns = 874, Max Conns = 874, Closing the
connection. These messages repeated, several times per minute, overnight and the next day until I restarted the server. The same thing happened again the next night.
A metalink search pointed to docid "293391.1" which, in part, suggests that the problem may be caused by improper programming, and that the solution may be to, "investigate the applications that connect to OID and where possible modify them to perform an explicit disconnect."
Does anyone have any reference to how an application can perform an explicit disconnect from the OID? We do have a relatively new application which follows the "Java API for Oracle Internet Directory" -- documention found here: http://download-west.oracle.com/docs/cd/B10501_01/network.920/a96577/oid_java.htm -- but in that document we cannot find any reference for how to "perform an explicit disconnect".
The application already calls the "context.close()" method, which according to the documentation closes the connection to the OID, but we cannot find any other "explicit disconnect". And, since the problem happens even though our app is already calling the context.close(), there must be something else.
Opened this up as a Metalink question related to Portal, but they said it's not their problem, and we should ask over here.
Any thoughts?

Looks like that's helped. While the errors persist, OID isn't dieing.
For anyone with similar problems, it looks like docid 437493.1 is useful. Upgrade clients to at least 10.2.0.3 to defeat a sqlnet problem.
Just tried it with the 10.2.0.5 patchset and it seems to be working and not generating the 104 error on the OID server.

Eclipse Error : javax.resource.cci.connection not found

Hi,
I am new to Eclipse development. I downloaded a Sap connector PAR project from sdn and imported it in Eclipse then i showed lots of error with portal.HTMLB, portal.connector and javax.resource.cci.connection.
I want to know where can i find the JAR file for this import? or how to resolve this problem?
Thank you
arun

Thanks Carlton and Jain,
I searched for the JAR files in the EP60 Installation directory usr\EP60,
.../additional-lib/connector.jar
.../additional-lib/com/sapportals/connectorframework/framework/GenericConnector.jar
.../additional-lib/com/sapportals/connectorframework/framework/ConnectorHelper.jar
.../additional-lib/jta.jar
.../portalapps/com.sap.portal.ivs.connectorservice/lib/com.sap.portal.ivs.connectorserviceapi.jar
I could find the names in the path specified by you but they are all ZIP files. When i Unzip them i could only find .class files inside them not the JAR files.
I resolved all the problems except Javax.cci import error.
If you have any idea where to find them it would help me a lot?
Thank you
arun

OID Max numbers of connections reached.

OID version 9.0.4.1.0. There're constant error messages '* ServerListener:2 * ERROR : ServerListener : Max numbers of connections reached. Num Conns
= 900, Max Conns = 900, Closing the connection." in the ldap.log file, but netstat -a|grep port|wc -l always return connections lower than 150.
I'd like to know what caused the error message being populated. Thanks

Looks like that's helped. While the errors persist, OID isn't dieing.
For anyone with similar problems, it looks like docid 437493.1 is useful. Upgrade clients to at least 10.2.0.3 to defeat a sqlnet problem.
Just tried it with the 10.2.0.5 patchset and it seems to be working and not generating the 104 error on the OID server.

Javax.resource.ResourceException: Failed to start the connection

I have created the JMS bridge in Weblogic10.0 to connect with MQ server, I am getting error when startingup the weblogic server. Below the error
####<28-Mar-2009 10:56:25 o'clock GMT> <Info> <MessagingBridge> <clx25ao02> <aauat100-02> <[STANDBY] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1238237785804> <BEA-200042> <Bridge MQ_TO_JMS_1 failed to connect to the source destination and will try again in 20 seconds. This could be a temporary condition unless the messages repeat several times. (javax.resource.ResourceException: Failed to start the connection)>
I deployed the JMS adaptor also in weblogic10.0.
Could you please tell me the reason for the error?

A problem occurred with a Messaging Bridge between two JMS topics running in two Managed
Servers in the same domain, running on the same machine. As the Messaging Bridge was being
started during WebLogic Server startup, it threw the following warning message. Messages
could not be forwarded.
Analysis revealed that the bridge failed to create the message listener because it was
configured for durable topics and there was no JMS store available. The Bridge encountered an
internal error when trying to log the resource exception so the customer was not able to tell
why the bridge was failing.
The problem was resolved by a code change to allow the bridge to throw the correct resource
exception. Now, the correct exception is logged by the bridge.

Missing type javax.resource.cci.connection

Hi,
I'm would like to use JCA framwork, but I guess I should have appropriate connection class.
the missing class type is javax.resource.cci.connection
Where can I find/download this class jar file?
Any help would be appriciated
Thanks
Ami

The error I get that prevent me from compiling the projects is:
This compilation unit indirectly references the missing type javax.resource.cci.Connection (typically some required class file is referencing a type outside the classpath)
any idea of what should I do?
Thanks
Ami

Restarting Apache on reaching Max Connections

Hi All,
We are using OAS 10.1.3.1 in Solaris environment. Presently we have set max connections to 350. Once connections reaches max, apache is getting hanged & it resumes once we restart services using opmnctl. Is there any way to make restart apache by itself, once it reaches max connections.
thanx & regards

hi...
the best thing you can do is increase the max connection value... is it a prod insatance? since normally for prod instances its a higher value.
Rgds...R

How to catch exception when have max connection pool

hi,
i have define in oracle user that i could have max 10 sessions at the same time.
I have jdbc datasource & connection pool defined at glassfish server(JSF application).
now, if in application is too many queries to the database then i have error: nullpointer exception - becouse when i try to do:
con = Database.createConnection(); - it generates nullpointer exception becouse there isn't free connection pool
i try to catch exception like this:
public List getrep_dws_wnioski_wstrzymane_graph() {     int i = 0;     try {     con = Database.createConnection();     ps =    (Statement) con.createStatement();     rs = ps.executeQuery("select data, klasa, ile_dni_wstrzymana, ile_wnioskow from stg1230.dwsww_wstrzymane_dws8 order by data, klasa, ile_dni_wstrzymana, ile_wnioskow");     while(rs.next()){       rep_dws_wnioski_wstrzymane_graph.add(i,new get_rep_dws_wnioski_wstrzymane_graph(rs.getString(1),rs.getString(2),rs.getString(3),rs.getString(4)));       i++;     }     } catch (NamingException e) {         e.printStackTrace();     } catch (SQLException e) {         e.printStackTrace();     } catch (NullPointerException e) {         e.printStackTrace();         throw new NoConnectionException(); // catch null 1     } finally {     try {         con.close();     } catch (SQLException e) {         e.printStackTrace();     } catch (NullPointerException e) {         e.printStackTrace();         throw new NoConnectionException(); // catch null 2     }     } return rep_dws_wnioski_wstrzymane_graph; }
but at line:
con.close();
i have nullpointerexception
and
at line
throw new NoConnectionException(); // catch null 2
i have: caused by exception.NoConnectionException
what's wrong with my exception class? how to resolve it?
public class NoConnectionException extends RuntimeException{     public NoConnectionException(String msg, Throwable cause){       super(msg, cause);     }     public NoConnectionException(){       super();     } }
at web.xml i have defined:
<error-page>         <exception-type>exception.NoConnectionException</exception-type>         <location>/NoConnectionExceptionPage.jsp</location>     </error-page>

thanks,
i did it and i have error:
java.sql.SQLException: Error in allocating a connection. Cause: Connection could not be allocated because: ORA-02391: exceeded simultaneous SESSIONS_PER_USER limit
at com.sun.gjc.spi.base.DataSource.getConnection(DataSource.java:115)
at logic.Database.createConnection(Database.java:37): conn = ds.getConnection();
public class Database {
     public static Connection createConnection() throws NamingException,
                SQLException {
            Connection conn = null;
            try{
                Context ctx = new InitialContext();
          if (ctx == null) {
               throw new NamingException("No initial context");
          DataSource ds = (DataSource) ctx.lookup("jdbc/OracleReports");
          if (ds == null) {
               throw new NamingException("No data source");
          conn = ds.getConnection(); // here's exception when max connections to database
          if (conn == null) {
               throw new SQLException("No database connection");
            } catch (NamingException e) {
                e.printStackTrace();
                throw new NoConnectionException();
         } catch (SQLException e) {
             e.printStackTrace();
                throw new NoConnectionException();
            catch (NullPointerException e) {
             e.printStackTrace();
                throw new NoConnectionException(); // obsluga bledy na wypadek jesli braknie wolnych polaczen do bazy
        return conn;
}and at my ealier code i have error:
at logic.GetDataOracle.getrep_dws_wnioski_wstrzymane_graph(GetDataOracle.java:192)
at line: con = Database.createConnection();
in code:
public List getrep_dws_wnioski_wstrzymane_graph() {
    int i = 0;
    try {
    con = Database.createConnection();
    ps =    (Statement) con.createStatement();
    rs = ps.executeQuery("select data, klasa, ile_dni_wstrzymana, ile_wnioskow from stg1230.dwsww_wstrzymane_dws8 order by data, klasa, ile_dni_wstrzymana, ile_wnioskow");
    while(rs.next()){
      rep_dws_wnioski_wstrzymane_graph.add(i,new get_rep_dws_wnioski_wstrzymane_graph(rs.getString(1),rs.getString(2),rs.getString(3),rs.getString(4)));
      i++;
    } catch (NamingException e) {
        e.printStackTrace();
    } catch (SQLException e) {
        e.printStackTrace();
    } catch (NullPointerException e) {
        e.printStackTrace();
        throw new NoConnectionException();
    } finally {
    try {
        if(con != null)
        con.close();
    } catch (SQLException e) {
        e.printStackTrace();
    } catch (NullPointerException e) {
        e.printStackTrace();
        throw new NoConnectionException();
return rep_dws_wnioski_wstrzymane_graph;
}so what's wrong?
i have limit max sessions 10 at oracle so i set at my connection pool 5 connections as max. But when i get max 5 sesssins and try to execute next query then i can't catch exception..

Error in resource adapter cleanup.. javax.resource.ResourceException: java.

Hi,
I am getting the following error in my Oracle AS 10g R3 on Solaris .
Error in resource adapter cleanup.. javax.resource.ResourceException: java.sql.SQLException: Closed Connection
in log file:apps/oracle/oc4j_home/j2ee/homeMYAPP/log/homeMYAPP_default_group_1/oc4j/log.xml
(Click on the log file link to download the log or view it as plain text)
Can any one explain why this error comes.
Regards,
Kumar

Hi,
I am getting the following error in my Oracle AS 10g R3 on Solaris .
Error in resource adapter cleanup.. javax.resource.ResourceException: java.sql.SQLException: Closed Connection
in log file:apps/oracle/oc4j_home/j2ee/homeMYAPP/log/homeMYAPP_default_group_1/oc4j/log.xml
(Click on the log file link to download the log or view it as plain text)
Can any one explain why this error comes.
Regards,
Kumar

Javax.resource.cci interface

          Hi.
          I´m getting a bit frustrated by now. My contact at BEA wont answer my questiona...
          I am (still) trying to get my adapter to work on WL 6.1 SP1-2.
          The adapter I´m using (trying anyway) implements the javax.resource.cci interface.
          BUT, when I´m trying to reference it (the adapter) from an EJB in the ejb-jar.xml
          descriptor, I get an error message from ejbc.
          When I try to edit the descriptor from within the Admin Console, the interface
          is not available in the dropdown menu.
          So, the question I have to ask: Does WL 6.1 support the cci-interface?
          This is it, if I can´t work it out by Friday I will have to tell our customer
          that WebLogic is not the way to go. I´d hate to do that...
          regards,
          Oskar


          Hi Timothy.
          Thanks for answering.
          When referencing an adapter from an EJB, you are supposed to make that reference
          in ejb-jar.xml (attached). But the resource type <res-type> that is supposed to
          be used is javax.resource.cci.ConnectionFactory.
          However if you try to set that resource type in the Admin Console, that option
          is not available. It is not present in the drop-down box.
          The same thing goes for ejbc. When I try to compile with ejbc I get the following
          error:
          ejbc:
          [java] ERROR: Error processing 'ejb-jar.xml': .ejb-jar.enterprise-beans.session.resource-ref.res-type.
          must be one of the values: javax.sql.DataSource,javax.jms.QueueConnectionFactory,javax.jms.TopicConnectionFactory,java.net.URL,javax.mail.Session
          [java] ERROR: ejbc found errors
          Which seems like the same thing.
          I would much appreciate any help, my time is running out.
          Thanks
          Oskar
          "Timothy Potter" <[email protected]> wrote:
          >Dear Oskar,
          >
          >I'm sorry to hear that you are not getting the support you need. An
          >application server doesn't actually care about your client interface,
          >so yes
          >WebLogic does support CCI so to speak. The application server only cares
          >about your adapter's SPI. What is the specific error message from ejbc?
          >Also, can you attach your ejb-jar.xml file so that I can see what interface
          >you are referencing?
          >
          >Best regards,
          >
          >Timothy Potter
          >Senior Software Engineer
          >eCommerce Server Division
          >BEA Systems, Inc.
          >

ORA - Maximum Connections Reached

Dear All
Even after implementing Connection pooling in our Application , we very often get this error "150 process exceede- Maximum Connection reached" ? How do we handle this? Our application is about to GoLive in another month .Please help us.
Thanks
AKS

It was simple to plan a download calendar in the case of exceeding maximum connections.
I think this rerolve.
1-"In this momment isn't not possible too manny connections"
2-Please your type of modem: xpto / xpt1 / xpt2 / etc...
3-Calculating 'tracert time'
3-Calculating time max: x minutes min: y minutes
4-Plan a download time:
TODAY DD1/MM1/YYYY1
-HOURS-
10 -
11 -
12
13 -
DD1/MM1/YYYY1
10
11 -
12 -
13
14
15 -
DD1/MM1/YYYY1
10
11
12
13 -
14 -
15
..

Changing Max-Connections in CSS 11500

I have an architecture with two 11500 in active-passive mode and receive 800 connections every 5 minutes.
Could appear secondaries effects if i change the default of max-connections in CSS 11500 for example to 1200?
One of the risks i want to avoid is with this change, the CSS could be crashdown because of the drop of connections..

Good morning,
Could you please let me know what is the exact parameter you are talking about?
From what you described, I believe you may be referring to the "max connections" parameter configured under the services. This command just limits the number of concurrent connections that are allowed on a specific real server to ensure that the server itself doesn't get overloaded. Increasing this limt would not have any negative effect on the CSS itself, but, since you are allowing more simultaneous connections on the server, you may experience resource issues on the server itself.

JDBC Connection pools and clusters (is max connection for entire cluster?)

Hi,
Quick question.
When using JDBC connection pools in WAS 6.40 (SP13) in a clustered environment. Are the max connections the number
a)Each application server can use
b)The entire cluster can use
Would believe a), but I'd like it confirmed from someoneelse

Hi Dagfinn,
your assumption is correct. Therefore, in a cluster environment you'd need to make sure the DB can open <i>Number of nodes X max connections</i>.

Javax.resource.spi.ResourceAdapterInternalException: max connections reache

Similar Messages

Maybe you are looking for