Exception when stopping LogBack context

I am using LogBack's JMX capabilities but are getting an error when trying to stop the logger context in the contexDestroyed method
of a context listener. It seems there is a security issue when unregistering the LogBack JMX Configurator mbean. The web
application is deployed on a managed server. Has anyone seen this before?
####<2013-11-11 15:07:21.555 +0100 CET> <Warning> <HTTP> <sde-jeb104-sn0.ref.utv.skanova.net> <sde-te104-slee-sip20-d81-ms1-i1> <[ACTIVE] ExecuteThread: '17' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <> <1384178841555> <BEA-101162> <User defined listener com.ts.sde.bb.logging.listener.JmxCleanupContextListener failed: weblogic.management.NoAccessRuntimeException: Access not allowed for subject: principals=[], on ResourceType: ch.qos.logback.classic.jmx.JMXConfigurator Action: unregister, Target: null.
weblogic.management.NoAccessRuntimeException: Access not allowed for subject: principals=[], on ResourceType: ch.qos.logback.classic.jmx.JMXConfigurator Action: unregister, Target: null
 at weblogic.management.internal.SecurityHelper$IsAccessAllowedPrivilegeAction.wlsRun(SecurityHelper.java:819)
 at weblogic.management.internal.SecurityHelper$IsAccessAllowedPrivilegeAction.run(SecurityHelper.java:682)
 at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
 at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
 at weblogic.management.internal.SecurityHelper.isAccessAllowed(SecurityHelper.java:269)
 at weblogic.management.internal.SecurityHelper.isAccessAllowed(SecurityHelper.java:158)
 at weblogic.management.mbeanservers.internal.SecurityInterceptor.checkUnregisterSecurity(SecurityInterceptor.java:672)
 at weblogic.management.mbeanservers.internal.SecurityInterceptor.unregisterMBean(SecurityInterceptor.java:321)
 at weblogic.management.jmx.mbeanserver.WLSMBeanServer.unregisterMBean(WLSMBeanServer.java:210)
 at ch.qos.logback.classic.jmx.JMXConfigurator.onStop(JMXConfigurator.java:249)
 at ch.qos.logback.classic.LoggerContext.fireOnStop(LoggerContext.java:334)
 at ch.qos.logback.classic.LoggerContext.stop(LoggerContext.java:352)
 at com.ts.sde.bb.logging.listener.JmxCleanupContextListener.contextDestroyed(JmxCleanupContextListener.java:32)
 at weblogic.servlet.internal.EventsManager$FireContextListenerAction.run(EventsManager.java:482)
 at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
 at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
 at weblogic.servlet.internal.EventsManager.notifyContextDestroyedEvent(EventsManager.java:200)
 at weblogic.servlet.internal.WebAppServletContext.destroy(Unknown Source)
 at weblogic.servlet.internal.ServletContextManager.destroyContext(ServletContextManager.java:241)
 at weblogic.servlet.internal.HttpServer.unloadWebApp(HttpServer.java:461)
 at weblogic.servlet.internal.WebAppModule.destroyContexts(WebAppModule.java:1540)
 at weblogic.servlet.internal.WebAppModule.deactivate(WebAppModule.java:513)
 at weblogic.application.internal.flow.ModuleStateDriver$2.previous(ModuleStateDriver.java:389)
 at weblogic.application.utils.StateMachineDriver.previousState(StateMachineDriver.java:167)
 at weblogic.application.utils.StateMachineDriver.previousState(StateMachineDriver.java:160)
 at weblogic.application.internal.flow.ModuleStateDriver.deactivate(ModuleStateDriver.java:141)
 at weblogic.application.internal.flow.ScopedModuleDriver.deactivate(ScopedModuleDriver.java:207)
 at weblogic.application.internal.flow.ModuleListenerInvoker.deactivate(ModuleListenerInvoker.java:261)
 at weblogic.application.internal.flow.DeploymentCallbackFlow$2.previous(DeploymentCallbackFlow.java:538)
 at weblogic.application.utils.StateMachineDriver.previousState(StateMachineDriver.java:167)
 at weblogic.application.utils.StateMachineDriver.previousState(StateMachineDriver.java:160)
 at weblogic.application.internal.flow.DeploymentCallbackFlow.deactivate(DeploymentCallbackFlow.java:182)
 at weblogic.application.internal.flow.DeploymentCallbackFlow.deactivate(DeploymentCallbackFlow.java:175)
 at weblogic.application.internal.BaseDeployment$2.previous(BaseDeployment.java:1281)
 at weblogic.application.utils.StateMachineDriver.previousState(StateMachineDriver.java:167)
 at weblogic.application.utils.StateMachineDriver.previousState(StateMachineDriver.java:160)
 at weblogic.application.internal.BaseDeployment.deactivate(BaseDeployment.java:453)
 at weblogic.application.internal.SingleModuleDeployment.deactivate(SingleModuleDeployment.java:43)
 at weblogic.application.internal.DeploymentStateChecker.deactivate(DeploymentStateChecker.java:199)
 at weblogic.deploy.internal.targetserver.AppContainerInvoker.deactivate(AppContainerInvoker.java:98)
 at weblogic.deploy.internal.targetserver.BasicDeployment.deactivate(BasicDeployment.java:263)
 at weblogic.deploy.internal.targetserver.BasicDeployment.deactivateFromServerLifecycle(BasicDeployment.java:458)
 at weblogic.management.deploy.internal.DeploymentAdapter$1.doDeactivate(DeploymentAdapter.java:74)
 at weblogic.management.deploy.internal.DeploymentAdapter.deactivate(DeploymentAdapter.java:215)
 at weblogic.management.deploy.internal.AppTransition$6.transitionApp(AppTransition.java:67)
 at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:240)
 at weblogic.management.deploy.internal.ConfiguredDeployments.deactivate(ConfiguredDeployments.java:199)
 at weblogic.management.deploy.internal.ConfiguredDeployments.undeploy(ConfiguredDeployments.java:191)
 at weblogic.management.deploy.internal.DeploymentServerService.shutdownApps(DeploymentServerService.java:195)
 at weblogic.management.deploy.internal.DeploymentServerService.shutdownHelper(DeploymentServerService.java:127)
 at weblogic.application.ApplicationShutdownService.halt(ApplicationShutdownService.java:143)
 at weblogic.t3.srvr.ServerServicesManager.haltInternal(ServerServicesManager.java:504)
 at weblogic.t3.srvr.ServerServicesManager.halt(ServerServicesManager.java:336)
 at weblogic.t3.srvr.T3Srvr.shutdown(T3Srvr.java:1039)
 at weblogic.t3.srvr.T3Srvr.forceShutdown(T3Srvr.java:946)
 at weblogic.t3.srvr.ServerRuntime.forceShutdown(ServerRuntime.java:351)
 at weblogic.server.RemoteLifeCycleOperationsImpl.forceShutdown(RemoteLifeCycleOperationsImpl.java:59)
 at weblogic.server.RemoteLifeCycleOperationsImpl_WLSkel.invoke(Unknown Source)
 at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:590)
 at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:478)
 at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
 at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:147)
 at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:473)
 at weblogic.rmi.internal.wls.WLSExecuteRequest.run(WLSExecuteRequest.java:119)
 at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
 at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)

Hi,
How did you upgrade JDeveloper? You should install new releases of JDeveloper into a new, empty directory, not over the top of any existing installation. I'm not sure if this is the cause of your problem, but we've seen many other issues in the past due to this.
Thanks,
Brian
JDev Team

Similar Messages

NO_PERMISSION Exception when calling secured EJB-methods

In WL6.1, I have an Ejb with secured methods. The (Swing) client application accesses the Ejb through rmi-iiop using the JDK1.3.1 Orb.
Unfortunately, it seems that the caller identity (which was supplied in the InitialContext lookup) is not propagated
to the server: any call to a secured method
fails with a CORBA NO_PERMISSION Exception.
Non secured methods work fine.
Using the t3 protocol the program also works fine, but that would require
the 25Mb weblogic.jar on all clients,
which is unattainable for us.
Any ideas how this situation can be corrected?
-Allard Siemelink

I am still getting the NO_PERMISSION Exception when using "weblogic.jndi.WLInitialContextFactory".
We use Sun's JRE, version 1.3.1_01.
Am I forgetting something?
My code is as follows:
InitialContext context = null;
try {
Hashtable ht = new Hashtable();
ht.put(InitialContext.INITIAL_CONTEXT_FACTORY, "weblogic.jndi.WLInitialContextFactory");
ht.put(InitialContext.PROVIDER_URL, "iiop://localhost:80");
ht.put(InitialContext.SECURITY_PRINCIPAL, "system");
ht.put(InitialContext.SECURITY_CREDENTIALS, "system_password");
context = new InitialContext(ht);
Object objHome = context.lookup(EJB_NAME);
MyHome myHome = (MyHome)PortableRemoteObject.narrow(objHome, MyHome.class);
MyRemote myRemote = myHome.create();
//NEXT LINE Crashes when method is secured:
myRemote.securedMethod();
finally {
if (context!=null) context.close();
Andy Piper <[email protected]> wrote:
Allard Siemelink <[email protected]> writes:
In WL6.1, I have an Ejb with secured methods. The (Swing) client applicationaccesses the Ejb through rmi-iiop using the JDK1.3.1 Orb.
Unfortunately, it seems that the caller identity (which was suppliedin the InitialContext lookup) is not propagated
to the server: any call to a secured method
fails with a CORBA NO_PERMISSION Exception.Make sure you are using WLInitialContextFactory and not
CNCtxFactory. Only the former will give you security.
andy

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..

Getting exception when trying to open Alert Configuration in RW

Hello friends,
I am getting the following exception when i am trying to open the Alert Configuration/Alert Inbox in RWB.
Exception:
com.sap.aii.rwb.exceptions.BuildLandscapeException: No central monitoring server in exchange profile
        at com.sap.aii.rwb.core.MonitoringServer.(MonitoringServer.java:77)
        at com.sap.aii.rwb.agent.server.SLDAgentBean.buildMonitoringServer(SLDAgentBean.java:799)
        at com.sap.aii.rwb.agent.server.SLDAgentBean.getMonitoringServer(SLDAgentBean.java:1462)
        at com.sap.aii.rwb.agent.api.SLDAgentObjectImpl0.getMonitoringServer(SLDAgentObjectImpl0.java:999)
        at com.sap.aii.rwb.agent.api.SLDAgent_Stub.getMonitoringServer(SLDAgent_Stub.java:1931)
        at com.sap.aii.rwb.agent.client.EJBAgent.getMonitoringServer(EJBAgent.java:493)
        at jsp_alert_inbox1204719699497._jspService(jsp_alert_inbox1204719699497.java:28)
        at com.sap.engine.services.servlets_jsp.server.jsp.JspBase.service(JspBase.java:112)
        at com.sap.engine.services.servlets_jsp.server.servlet.JSPServlet.service(JSPServlet.java:544)
        at com.sap.engine.services.servlets_jsp.server.servlet.JSPServlet.service(JSPServlet.java:186)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
        at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.doWork(RequestDispatcherImpl.java:321)
        at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:377)
        at jsp_FC_Secure1204104271605._jspService(jsp_FC_Secure1204104271605.java:24)
        at com.sap.engine.services.servlets_jsp.server.jsp.JspBase.service(JspBase.java:112)
        at com.sap.engine.services.servlets_jsp.server.servlet.JSPServlet.service(JSPServlet.java:544)
        at com.sap.engine.services.servlets_jsp.server.servlet.JSPServlet.service(JSPServlet.java:186)
        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:100)
        at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
Could you please help me out in solving this problem?
Thanks & Regards,
Senthil

From your error, maybe your profile parameter for alert message server is not properly configured:
I just came cross a post elaborating alerting configuration from Aashish Sinha, hope it helps,
Liang
=====Post from Aashish Sinha=======
Prerequisites
The following prerequisites have to be met in order to use the Alert Management (ALM):
· For using the Alert Inbox (BSP based display program of ALM), the corresponding service has to be activated in the service maintenance transaction SICF. Choose Default_host ? sap ? bc ? bsp ? sap ? alert inbox, and Activate in the context menu.
· For customizing or administration of the Alert Management the corresponding authorization role has to be assigned. The end users do not need any additional authorization.
· The central alert server must be maintained as an RFC destination in transaction SM59 in the local system. If there is no suitable user, you have to create a user for the RFC connection in the central alert system in transaction SU01. To make this RFC destination known as the RFC destination of the Alert Management System in the local system, the central alert server must also be selected as the RFC destination in transaction SALRT1 of the local system or in Settings ? RFC-Destination of Alert Server.
If the central alert server is running on the local system in the same client, you do not have to maintain an RFC destination. In this case, you can simply enter NONE in transaction SALRT1.
· If external communication types, such as e-mail, SMS, and fax are used, these communication types must be correctly configured in SAPconnect, because the alerts are then sent from the central alert system via SAPconnect.
Process Flow
The following describes the process flow from alert configuration (transaction ALRTCATDEF) to alert display and confirmation (for example in the alert inbox transaction ALRTINBOX):
1. Optional: You can define alert classifications. These are useful to group alert categories. For example, you can create an alert classification CRM that contains alert categories referring to CRM. Alert classifications can now have subclassifications. This enables you to build up your own classification hierarchy. Especially, if you use the Alert Mangement (ALM) extensively, classification and subclassification help you to organize your ALM alert landscape and to have a clear overview.
2. For different types of alerts you have to define different categories. The category contains various properties and other specifications that define the alerts within that category, for example expiry date, or the escalation recipient. You can define an alert category to suit your business requirements and assign the category to the corresponding classification. For example, for the alert classification CRM you can create the alert categories Contract Cancelled and Decrease in Sales. When the critical situation defined in the alert category arises, the system recognizes this and sends an alert instance of this category to the recipients determined. The alerts can always be found in the display programs configured for the recipient (UWL, application-specific program, or alert inbox). Additionally, the alerts are sent via eventual external communication channels, such as e-mail, sms, or fax.
3. You have to determine recipients so that the Alert Management knows who the recipients of alerts of a particular category are and that the correct parties are informed.
4. You can configure the way how alerts are processed. For the general use of the Alert Management you do not have to change the default settings. However, if for example you want to send alerts to third-party systems, or to be able to confirm alerts by SMS/Internet mail, or to have logs written, then you have to configure alert processing.
5. There is a number of Alert Management administration reports that you must schedule according to your requirements. For example, report RSALERTPROC must be executed in order to enable escalation.
6. Alerts of a particular category must be triggered by an application at runtime. Triggering alerts can be done in various ways. You can call a function module directly or use middleware components that trigger alerts, such as the Business Object Repository (BOR), Post Processing Framework (PPF), SAP Workflow, or CCMS.
7. Recipients can view the alerts assigned to them in the UWL of Enteprise Portal, in application-specific display programs, or in the alert inbox. In addition, alerts can be received as e-mail, SMS, or fax, if these external communication channels are configured in SAPconnect.
8. If the problem causing the alert is solved by a recipient, the recipient can confirm the alert, this means its status is changed and it will not be delivered, escalated, or displayed anymore. Alerts are generally confirmed by the recipient in the display program, such as the UWL or Alert Inbox. However, if an alert is sent by Internet mail or SMS message, it is also possible to confirm it by sending an Internet mail or SMS message back to the SAP system. Alert Management uses inbound processing for this.
Hope this will help you.
Regards
Aashish Sinha
============End of the Post=======================

Exception in thread "main" Context Value Management Failed.

Hi
I am facing one issue when i regenerate autoconfig.
We are running Multi Node installation of Oracle EBS on SUN O.S, and
when I regenerate Autoconfig, I am getting
Using AutoConfig to configure the Applications environment
Loading APPL_TOP environment from /u11/oracle/k24eb1appl
Verifying Context file ...
found context version : 115.121
minimum required version : 115.121
available update version : 115.178
An update for the Context File is available.
java.lang.NullPointerException
at oracle.apps.ad.context.CtxValueMgt.main(Compiled Code)
Exception in thread "main" Context Value Management Failed.
Exiting with status 1
Any Solutions pls
Reg
Sundar

Cross posted in java-forums.
OP, please do not cross-post without notification such as links to the other cross-posts. Nobody likes duplicating work that's already been done.

Exception when opening migrating From Jdev9.02 to 9.03

I am getting the following exception when migrating my project from Jdeveloper 9.02 to 9.031 version.
Below is the Exception Stack trace
java.lang.NullPointerException
     void oracle.ideimpl.scm.impl.BufferWatcher.handleWatchEvent()
          BufferWatcher.java:135
     java.util.List oracle.ideimpl.scm.env.OperationRuntimeImpl.performImpl(oracle.ide.scm.SCMOperation, java.util.List, boolean)
          OperationRuntimeImpl.java:207
     void oracle.ideimpl.scm.impl.ActionController.handleEventImpl(oracle.ide.scm.SCMOperation, oracle.ide.IdeAction, oracle.ide.addin.Context)
          ActionController.java:604
     void oracle.ideimpl.scm.impl.ActionController.access$2000071(oracle.ideimpl.scm.impl.ActionController, oracle.ide.scm.SCMOperation, oracle.ide.IdeAction, oracle.ide.addin.Context)
          ActionController.java:68
     void oracle.ideimpl.scm.impl.ActionController$1.run()
          ActionController.java:181
     void oracle.ideimpl.scm.impl.OperationThread$ThreadRunnable.run()
          OperationThread.java:212
     void oracle.ideimpl.scm.impl.OperationThread$ThreadRunnable.access$2000071(oracle.ideimpl.scm.impl.OperationThread$ThreadRunnable)
          OperationThread.java:184
     void oracle.ideimpl.scm.impl.OperationThread.run()
          OperationThread.java:157

Hi,
How did you upgrade JDeveloper? You should install new releases of JDeveloper into a new, empty directory, not over the top of any existing installation. I'm not sure if this is the cause of your problem, but we've seen many other issues in the past due to this.
Thanks,
Brian
JDev Team

Exception when running WLST in Eclipse - Please Help!!!

Hello,
I am trying to get get a WLST online connection via a java class, but I am getting an exception when trying to connect to an admin server instance:
 
 javax.naming.CommunicationException [Root exception is java.rmi.ConnectIOException: error during JRMP connection establishment; nested exception is:
 java.io.EOFException]
 at weblogic.jrmp.Context.lookup(Context.java:189)
 at weblogic.jrmp.Context.lookup(Context.java:195)
 at javax.naming.InitialContext.lookup(InitialContext.java:351)
 at weblogic.management.scripting.WLSTHelper.initDeprecatedConnection(WLSTHelper.java:546)
 at weblogic.management.scripting.WLSTHelper.initConnections(WLSTHelper.java:285)
 
 
The CompatabilityMBeanServer is not initialized properly. This might happen if the CompatabilityMBeanServer is disabled via the JMXMBean.To view the real exception use dumpStack()
WLST detected that the RuntimeMBeanServer is not enabled. This might
happen if the RuntimeMBeanServer is disabled via the JMXMBean.
Please ensure that this MBeanServer is enabled. Online WLST cannot function
without this MBeanServer.
 
 
I am basically trying to run the following WLST command in java:
connect('weblogic','weblogic','t3://localhost:7201')
 
 
Here is the java block that I call to create the connection with the WLSTIterpreter:
 
 
StringBuffer buffer = new StringBuffer();
buffer.append("connect('weblogic','weblogic','t3://localhost:7201')\n"); System.out.println(buffer.toString());
 
INTERPRETER.exec(buffer.toString());
 
 
My admin server is running at this address and the CompatabilityMBeanServer is enabled. The strange thing this is that I am able to run the WLST via the command line and the connection is successful with no problems. This leads me to believe that there is something wrong with my classpath/environment that I have setup in Eclipse but I am not sure.
Any ideas on where I went wrong??? Please help!
Thanks :)
PS. I am running WebLogic 9.1 and java 150_06
Message was edited by:
rogaljo

I also have a similar issue (JNDI lookup works on the command line but not in Eclipse).
I posted another topic regarding this today with the title:
"CommunicationException ..."
In the groups:
weblogic...jndi
weblogic...jdbc

Post install failing with Java Exception creating the Oracle Context

I have not been able to complete the post-install portion of the OID which is run by the Oracle 9iAS Infrastructure installer.
Is there a way to create the Oracle Context and whatever else is part of the /ldap/postcfg/postcfg script without the use of the Java assistants? I am getting a Java exception when creating the Oracle Context.
Thanks,
e.

are you trying to install ias on Linux or windows??

Urgent: How can I catch the exception when application exit by accident

Can anyone give me advice and idea?
I want to catch the exception when application goes down by accident for example: Power off, turn off the machine without closing the appliction properly.
Because I want to notify the server and remove it from register.
How can I do this????
Please help,
Thanks very mich,
Peter

Shrubz,
I tested my application as follows:
1. start rmiregistry
2. start rmi server
3. start two clients
I printed out the client's object information as below:
first clinet:
RemoteObserver is com.ss8.qos.qcsm.policy.policyui.PanelMain_Stub[RemoteStub [ref: [endpoint:[192.168.70.237:4706](remote),objID:[-73a6662b:e75af455a5:-8000, 0]]]]
second client:
RemoteObserver is com.ss8.qos.qcsm.policy.policyui.PanelMain_Stub[RemoteStub [ref: [endpoint:[192.168.70.237:4711](remote),objID:[-73a6665a:e75af48703:-8000, 0]]]]
Now I stop the second client by clicking ^C (ctrl c)
I noticed that this client has not been removed from the server register (Vector).
next, I am working on first client for example add one record. After server received this record, it will update all clients who have already registered with server. Because now in the server register there are two clinets (first and second), so it will try to update two clients. The exception will be thrown when server tries to update second client which has already been stoped. I used printStackTrace() to print out the message as follow:
Catch ConnectException
Connection refused to host: 192.168.70.237; nested exception is:
 java.net.ConnectException: Connection refused: no further information
java.rmi.ConnectException: Connection refused to host: 192.168.70.237; nested exception is:
 java.net.ConnectException: Connection refused: no further information
java.net.ConnectException: Connection refused: no further information
 at java.net.PlainSocketImpl.socketConnect(Native Method)
 at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:305)
 at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:125)
 at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:112)
 at java.net.Socket.<init>(Socket.java:269)
 at java.net.Socket.<init>(Socket.java:98)
 at sun.rmi.transport.proxy.RMIDirectSocketFactory.createSocket(RMIDirectSocketFactory.java:29)
 at sun.rmi.transport.proxy.RMIMasterSocketFactory.createSocket(RMIMasterSocketFactory.java:124)
 at sun.rmi.transport.tcp.TCPEndpoint.newSocket(TCPEndpoint.java:497)
 at sun.rmi.transport.tcp.TCPChannel.createConnection(TCPChannel.java:194)
 at sun.rmi.transport.tcp.TCPChannel.newConnection(TCPChannel.java:178)
 at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:87)
 at com.ss8.qos.qcsm.policy.policyui.PanelMain_Stub.update(PanelMain_Stub.java:53)
 at com.ss8.qos.qcsm.policy.policydb.Observable.performNotify(Observable.java, Compiled Code)
 at com.ss8.qos.qcsm.policy.policydb.Observable.notifyObservers(Observable.java:71)
 at com.ss8.qos.qcsm.policy.policydb.PolicyServer.ServerAddPolicy(PolicyServer.java:102)
 at java.lang.reflect.Method.invoke(Native Method)
 at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:237)
 at sun.rmi.transport.Transport$1.run(Transport.java:140)
 at java.security.AccessController.doPrivileged(Native Method)
 at sun.rmi.transport.Transport.serviceCall(Transport.java:137)
 at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:422)
 at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:634)
 at java.lang.Thread.run(Thread.java:479)
*** end here ***
I don't see any information related to object ID. How can I handle this?
Please give me suggestion.
Many Thanks,
Peter

Running in to Exceptions when implementing AjaxAutoSugest

Hi,
Seeing exception when running an application implementing AjaxAutoSugest which is documented @
http://www.oracle.com/technology/products/jdev/tips/mills/AjaxAutoSuggest/AjaxAutoSuggest.html
and the exception is
<Oct 12, 2009 11:51:38 AM CDT> <Error> <HTTP> <BEA-101020> <[ServletContext@17590159[app:AutoSuggestInputTextDemo module:AutoSuggestInputTextDemo-AutoSuggestTest-context-root path:/AutoSuggestInputTextDemo-AutoSuggestTest-context-root spec-version:2.5]] Servlet failed with Exception
java.lang.IllegalStateException: Response already committed
 at weblogic.servlet.internal.ServletResponseImpl.objectIfCommitted(ServletResponseImpl.java:1586)
 at weblogic.servlet.internal.ServletResponseImpl.sendRedirect(ServletResponseImpl.java:859)
 at javax.servlet.http.HttpServletResponseWrapper.sendRedirect(HttpServletResponseWrapper.java:136)
 at com.sun.faces.context.ExternalContextImpl.redirect(ExternalContextImpl.java:421)
 at org.apache.myfaces.trinidad.context.ExternalContextDecorator.redirect(ExternalContextDecorator.java:303)
 Truncated. see log file for complete stacktrace
>
<Oct 12, 2009 11:51:38 AM CDT> <Error> <HTTP> <BEA-101020> <[ServletContext@17590159[app:AutoSuggestInputTextDemo module:AutoSuggestInputTextDemo-AutoSuggestTest-context-root path:/AutoSuggestInputTextDemo-AutoSuggestTest-context-root spec-version:2.5]] Servlet failed with Exception
java.lang.IllegalStateException: Response already committed
 at weblogic.servlet.internal.ServletResponseImpl.objectIfCommitted(ServletResponseImpl.java:1586)
 at weblogic.servlet.internal.ServletResponseImpl.sendRedirect(ServletResponseImpl.java:859)
 at javax.servlet.http.HttpServletResponseWrapper.sendRedirect(HttpServletResponseWrapper.java:136)
 at com.sun.faces.context.ExternalContextImpl.redirect(ExternalContextImpl.java:421)
 at org.apache.myfaces.trinidad.context.ExternalContextDecorator.redirect(ExternalContextDecorator.java:303)
 Truncated. see log file for complete stacktrace
>
Could any one please help me , why i am getting this error.
Thanks,
Murali

your exception shows "at org.apache.myfaces.trinidad.context.ExternalContextDecorator.redirect(ExternalContextDecorator.java:303)"
check here
Re: response.sendRedirect() doesnt work
logout button

Exception when accessing PCD object from WD code

Hi All,
I'm trying to implement iview properties for a Web Dynpro project according to the code on "Maximizing Web Dynpro for Java" book.
However, I'm getting "null" exception when running the following method:
public IAttributeSet getRoleAttributeSet(boolean reloadIt) {
    if (reloadIt) {
      roleAttributeSet = null;
    if (roleAttributeSet == null) {
      try {
        Hashtable env = new Hashtable();
        env.put(Constants.REQUESTED_ASPECT, PcmConstants.ASPECT_SEMANTICS);
        env.put(Context.SECURITY_PRINCIPAL, WDClientUser.getCurrentUser().getSAPUser());
        InitialContext iCtx = new InitialContext(env);
        roleAttributeSet = (IAttributeSet) iCtx.lookup(iViewPath);
      } catch (Exception e) {
    return roleAttributeSet;
The line "roleAttributeSet = (IAttributeSet) iCtx.lookup(iViewPath);" causes the exception.
I saw several examples in SDN but none of them worked for me.
examples like this: /message/2222425#2222425 [original link is broken]
I used this blog: /people/daniel.wroblewski/blog/2006/07/30/everything-you-wanted-to-know-about-the-pcd
and this PDF: https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/314ae7a5-0c01-0010-c198-9c7c5e8cee46
But get the same exception.
I tried to set the iview path with & without "pcd:" prefix - didn't help
I added the "PORTAL:sap.com/com.sap.portal.pcd.glservice" to my project - didn't help.
Also, I tried using ASPECT_ADMINISTRATOR instead of ASPECT_SEMANTICS and get the IAttributeSet by using IADMInbase interface - didn't help either.
I used this code:
IAdminBase result =(IAdminBase)iCtx.lookup(objectName);
IAttributeSet myIview = (IAttributeSet) result.getImplementation(IAdminBase.ATTRIBUTE_SET);
Can someone provide me STEP BY STEP solution for getting IAttributeSet of an iview through Web Dynpro code.
The iview path exists.
I tested the code on EP6 SP16 & SP17.
Thanks,
Omri

Hi Bharathwaj,
I tried using the sharing references:
PORTAL:sap.com/com.sap.portal.ivs.api_iviewf and
PORTAL:sap.com/com.sap.portal.pcd.glservice
both didn't help
I have 'com.sap.portal.ivs.api_iview_api.jar' under the 'lib' folder.
Omri

Exception when i try to deploy application to OC4J

Hi
Thank you for reading my post
i get the following exception when i try to deploy the application from Jdeveloper 10.1.3.1 to the same application server. that i download and install.
Binding web application(s) to site default-web-site begins...
Binding register web-module for application register to site default-web-site under context root register-register-context-root
Exception: NoClassDefFoundError: oracle/jbo/JboException
Operation failed with error:
oracle/jbo/JboException

Did you install adf runtime (tools -> adf runtime installer ->standalone oc4j)?

Exception when retreiveing list from JNDI when the list updates at the same time.

Hi
I get a Exception when i am retreiving a list from the jndi:
Start server side stack trace:
com.sun.java.util.collections.ConcurrentModificationException
at java.lang.Throwable.fillInStackTrace(Native Method)
at java.lang.Throwable.fillInStackTrace(Compiled Code)
at java.lang.Throwable.<init>(Compiled Code)
at java.lang.Exception.<init>(Compiled Code)
at java.lang.RuntimeException.<init>(Compiled Code)
at
com.sun.java.util.collections.ConcurrentModificationException.<init>(Concurr
entModificationException.java:48)
at com.sun.java.util.collections.HashMap$HashIterator.next(Compiled
Code)
at
weblogic.jndi.toolkit.ReadOnlyMapBasedNamingStore$1.nextElement(Compiled
Code)
at weblogic.jndi.toolkit.AbstractNamingEnumeration.next(Compiled
Code)
at
weblogic.jndi.toolkit.AbstractNamingEnumeration.nextElement(Compiled Code)
at
weblogic.utils.enumerations.BatchingEnumerationBase.nextBatch(Compiled Code)
at
weblogic.utils.enumerations.BatchingEnumerationBase_WLSkel.invoke(BatchingEn
umerationBase_WLSkel.java:66)
at weblogic.rmi.extensions.BasicServerObjectAdapter.invoke(Compiled
Code)
at
weblogic.rmi.extensions.BasicRequestHandler.handleRequest(Compiled Code)
at
weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:1
5)
at weblogic.kernel.ExecuteThread.run(Compiled Code)
End server side stack trace
It says in the documentation of the weblogic server that: if the jndi is
updated while you are retreiving the list from the server, you will only get
the old list.
And that is ok for me. But insted i get this exception that interupts the
list retreiving. And if i just catch this exception an just continue or
start again, it comes over and over.
the code that does this, is like this:
InitialContext context = new InitialContext(env);
NamingEnumeration list = context.listBindings("sid");
Vector copy = new Vector(10000,1000);
log("Initiating copy of JNDI list!");
try
while (list.hasMore())
copy.addElement(list.next());
catch (Exception e)
log("Copying interupted:" + e.toString());
How can i solve this ?
Is it a configuration of the server problem ?
Are ther other ways of retreiving the list ?
-Ståle Tomten

Be carefull - you read Object two times, so if you
have only one object you will get null after second
reading, and NullPointerException as a result if you
try to do smth with null.
Wrong:
while( inputFromServlet1.readObject() != null)
Object o = inputFromServlet1.readObject();Previous man example is also wrong because you
cannot declare anything in while
Sorry for this one... I certainly must have spent too much time on these fora ;-)
Thanks for the correction, by the way...
Correct:
Object o;
while( (o = inputFromServlet1.readObject()) != null)
String str = (String)o;
System.out.println("Got Object");

Page/JNI: Exception when trying to connect in 1,page/ContentFetcher InterruptedIOExce

We have upgraded to fro m 3.0.8 portal 3.0.9.8.2 9iAS 1.0.2.2 on database 8.1.7
the system is very fast and run for sometime but after a while we see the following errors in Jserv.log file.
this error causes the whole system to hang and we have to restart apache/jserv.
Any light on this issue will be helpful and very much appreciated.
thanks,
Sunil Bontha
25/07/2001 14:07:51:388 CEST] Viewer/oracle.discoiv.Disco4iv: init
[25/07/2001 14:07:51:388 CEST] Viewer/oracle.discoiv.Disco4iv: Initializing Discoverer 4i Viewer (4.1.37.82)
[25/07/2001 14:09:15:219 CEST] page/oracle.webdb.page.ParallelServlet: init
[25/07/2001 14:09:15:249 CEST] page/JNI: Cache is enabled.
[25/07/2001 14:09:15:299 CEST] page/Starting a pool of 25 handlers.
[25/07/2001 14:09:43:820 CEST] page/JNI: Exception when trying to connect in 1.
[25/07/2001 14:09:43:830 CEST] page/Timeout occurred, label=145 url=http://www.myserver.com/pls/pmsportal30/!PMSPORTAL30.wwpro_app_provider.execute_portlet [25/07/2001 14:09:43:830 CEST] page/ContentFetcher InterruptedIOException Caught, Fetcher Timedout name=content-fetcher23
[25/07/2001 14:09:43:840 CEST] page/JNI: Exception when trying to connect in 1.
[25/07/2001 14:09:43:840 CEST] page/Timeout occurred, label=293 url=http://www.myserver.com/pls/pmsportal30/!PMSPORTAL30.wwpro_app_provider.execute_portlet [25/07/2001 14:09:43:840 CEST] page/ContentFetcher InterruptedIOException Caught, Fetcher Timedout name=content-fetcher22
[25/07/2001 14:09:53:864 CEST] page/JNI: Exception when trying to connect in 1.

Hi Avi,
My application is a standalone application trying to access MBeans present in oc4j.
I tried
using the code
props.put(Context.INITIAL_CONTEXT_FACTORY ,"oracle.j2ee.rmi.RMIInitialContextFactory");
obj = (ManagementHome) ctx.lookup("ejb/mgmt/MEJB");
but i am getting the following error.
javax.naming.NameNotFoundException: ejb/mgmt/MEJB not found
at com.evermind.server.rmi.RMIClientContext.lookup(RMIClientContext.java
:45)
at javax.naming.InitialContext.lookup(InitialContext.java:351)
at TestMBean.doSomething(TestMBean.java:90)
at TestMBean.main(TestMBean.java:237)
java.lang.NullPointerException
at TestMBean.doSomething(TestMBean.java:107)
at TestMBean.main(TestMBean.java:237)
Regards
Siva

Error When stopping AddOn

We are getting this error when stopping our AddOn "Addon failed with exception; Event Type 6" even though the addon stops correctly hhow can we overcome this error

Hi,
You may check this: Addon 90000002 failed with exception; Event type 6
Thanks,
Gordon

Exception when stopping LogBack context

Similar Messages

Maybe you are looking for