Skip to Main Content
Forums

Integration

Announcement

For appeals, questions and feedback about Oracle Forums, please email oracle-forums-moderators_us@oracle.com. Technical questions should be asked in the appropriate category. Thank you!

java.lang.OutOfMemoryError: getNewTla when deploy ADF application to weblogic server

Guohua-OracleSep 9 2015 — edited Nov 26 2015

Hi All,

When I trying to deploy HcmTalent application to standaone server

<Sep 8, 2015 11:47:36 PM PDT> <Warning> <RMI> <BEA-080004> <An error was thrown by rmi server: javax.management.remote.rmi.RMIConnectionImpl.fetchNotifications(JIJ)

java.lang.OutOfMemoryError: getNewTla.

  1. java.lang.OutOfMemoryError: getNewTla

        at com.sun.jmx.remote.internal.ArrayNotificationBuffer.fetchNotifications(ArrayNotificationBuffer.java:459)

        at com.sun.jmx.remote.internal.ArrayNotificationBuffer$ShareBuffer.fetchNotifications(ArrayNotificationBuffer.java:209)

        at com.sun.jmx.remote.internal.ServerNotifForwarder.fetchNotifs(ServerNotifForwarder.java:258)

        at javax.management.remote.rmi.RMIConnectionImpl$2.run(RMIConnectionImpl.java:1227)

        at javax.management.remote.rmi.RMIConnectionImpl$2.run(RMIConnectionImpl.java:1225)

        Truncated. see log file for complete stacktrace

>

<Sep 8, 2015 11:47:36 PM PDT> <Error> <EJB> <BEA-010080> <An error occurred while attempting to process a message inside a message-driven bean: java.lang.OutOfMemoryError: getNewTla

Exception is : java.lang.OutOfMemoryError: getNewTla

        at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:511)

        at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:205)

        at oracle.jdbc.driver.T4Caqdq.doOAQDQ(T4Caqdq.java:183)

        at oracle.jdbc.driver.T4CConnection.doDequeue(T4CConnection.java:4711)

        at oracle.jdbc.driver.PhysicalConnection.dequeue(PhysicalConnection.java:17863)

        at oracle.jdbc.driver.PhysicalConnection.dequeue(PhysicalConnection.java:17949)

        at weblogic.jdbc.wrapper.PoolConnection_oracle_jdbc_driver_T4CConnection.dequeue(Unknown Source)

        at oracle.jms.AQjmsConsumer.jdbcConnectionDequeueCheck25242(AQjmsConsumer.java:1713)

        at oracle.jms.AQjmsConsumer.jdbcDequeue(AQjmsConsumer.java:1295)

        at oracle.jms.AQjmsConsumer.receiveFromAQ(AQjmsConsumer.java:1035)

        at oracle.jms.AQjmsConsumer.receiveFromAQ(AQjmsConsumer.java:960)

        at oracle.jms.AQjmsConsumer.receiveFromAQ(AQjmsConsumer.java:938)

        at oracle.jms.AQjmsConsumer.receive(AQjmsConsumer.java:790)

        at weblogic.ejb.container.internal.NewJMSMessagePoller$1.run(NewJMSMessagePoller.java:264)

        at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)

        at weblogic.ejb.container.internal.JMSConnectionPoller.doPrivilegedJMSAction(JMSConnectionPoller.java:2752)

        at weblogic.ejb.container.internal.NewJMSMessagePoller.processOneMessage(NewJMSMessagePoller.java:260)

        at weblogic.ejb.container.internal.NewJMSMessagePoller.run(NewJMSMessagePoller.java:120)

        at weblogic.ejb.container.internal.NewJMSMessagePoller.timerExpired(NewJMSMessagePoller.java:235)

        at weblogic.timers.internal.TimerImpl.run(TimerImpl.java:273)

        at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:545)

        at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256)

        at weblogic.work.ExecuteThread.run(ExecuteThread.java:221)

>

<Sep 8, 2015 11:47:36 PM PDT> <Warning> <oracle.as.ess> <ESS-06002> <Failed to close runtime service handle. oracle.as.scheduler.RuntimeServiceException: Commit/rollback failed.

  • oracle.as.scheduler.RuntimeServiceException: Commit/rollback failed.

        at oracle.as.scheduler.runtime.jdbc.RuntimeBeanImpl.close(RuntimeBeanImpl.java:1436)

        at oracle.as.scheduler.runtime.RuntimeImpl.close(RuntimeImpl.java:643)

        at oracle.as.scheduler.runtime.RuntimeStore.close(RuntimeStore.java:240)

        at oracle.as.scheduler.adapter.ra.EventsWorker.waitForWorkNotification(EventsWorker.java:609)

        at oracle.as.scheduler.adapter.ra.EventsWorker.run(EventsWorker.java:411)

        at weblogic.connector.security.layer.WorkImpl.runIt(WorkImpl.java:108)

        at weblogic.connector.security.layer.WorkImpl.run(WorkImpl.java:44)

        at weblogic.connector.work.WorkRequest.run(WorkRequest.java:95)

        at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:545)

        at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256)

        at weblogic.work.ExecuteThread.run(ExecuteThread.java:221)

Caused By: java.sql.SQLException: Protocol violation: [5]

        at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:502)

        at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:205)

        at oracle.jdbc.driver.T4C7Ocommoncall.doOROLLBACK(T4C7Ocommoncall.java:72)

        at oracle.jdbc.driver.T4CConnection.doRollback(T4CConnection.java:751)

        at oracle.jdbc.driver.PhysicalConnection.rollback(PhysicalConnection.java:5150)

        at weblogic.jdbc.wrapper.PoolConnection_oracle_jdbc_driver_T4CConnection.rollback(Unknown Source)

        at oracle.as.scheduler.runtime.jdbc.RuntimeBeanImpl.close(RuntimeBeanImpl.java:1410)

        at oracle.as.scheduler.runtime.RuntimeImpl.close(RuntimeImpl.java:642)

        at oracle.as.scheduler.runtime.RuntimeStore.close(RuntimeStore.java:240)

        at oracle.as.scheduler.adapter.ra.EventsWorker.waitForWorkNotification(EventsWorker.java:609)

        at oracle.as.scheduler.adapter.ra.EventsWorker.run(EventsWorker.java:411)

        at weblogic.connector.security.layer.WorkImpl.runIt(WorkImpl.java:108)

        at weblogic.connector.security.layer.WorkImpl.run(WorkImpl.java:44)

        at weblogic.connector.work.WorkRequest.run(WorkRequest.java:95)

        at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:545)

        at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256)

        at weblogic.work.ExecuteThread.run(ExecuteThread.java:221)

>

<Sep 8, 2015 11:47:36 PM PDT> <Warning> <oracle.as.ess> <ESS-06002> <Failed to close runtime service handle. oracle.as.scheduler.RuntimeServiceException: Commit/rollback failed.

  • oracle.as.scheduler.RuntimeServiceException: Commit/rollback failed.

        at oracle.as.scheduler.runtime.jdbc.RuntimeBeanImpl.close(RuntimeBeanImpl.java:1436)

        at oracle.as.scheduler.runtime.RuntimeImpl.close(RuntimeImpl.java:643)

        at oracle.as.scheduler.runtime.RuntimeStore.close(RuntimeStore.java:240)

        at oracle.as.scheduler.adapter.ra.EventsWorker.waitForWorkNotification(EventsWorker.java:609)

        at oracle.as.scheduler.adapter.ra.EventsWorker.run(EventsWorker.java:411)

        at weblogic.connector.security.layer.WorkImpl.runIt(WorkImpl.java:108)

        at weblogic.connector.security.layer.WorkImpl.run(WorkImpl.java:44)

        at weblogic.connector.work.WorkRequest.run(WorkRequest.java:95)

        at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:545)

        at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256)

        at weblogic.work.ExecuteThread.run(ExecuteThread.java:221)

Caused By: java.sql.SQLException: Protocol violation: [5]

        at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:502)

        at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:205)

        at oracle.jdbc.driver.T4C7Ocommoncall.doOROLLBACK(T4C7Ocommoncall.java:72)

        at oracle.jdbc.driver.T4CConnection.doRollback(T4CConnection.java:751)

        at oracle.jdbc.driver.PhysicalConnection.rollback(PhysicalConnection.java:5150)

        at weblogic.jdbc.wrapper.PoolConnection_oracle_jdbc_driver_T4CConnection.rollback(Unknown Source)

        at oracle.as.scheduler.runtime.jdbc.RuntimeBeanImpl.close(RuntimeBeanImpl.java:1410)

        at oracle.as.scheduler.runtime.RuntimeImpl.close(RuntimeImpl.java:642)

        at oracle.as.scheduler.runtime.RuntimeStore.close(RuntimeStore.java:240)

        at oracle.as.scheduler.adapter.ra.EventsWorker.waitForWorkNotification(EventsWorker.java:609)

        at oracle.as.scheduler.adapter.ra.EventsWorker.run(EventsWorker.java:411)

        at weblogic.connector.security.layer.WorkImpl.runIt(WorkImpl.java:108)

        at weblogic.connector.security.layer.WorkImpl.run(WorkImpl.java:44)

        at weblogic.connector.work.WorkRequest.run(WorkRequest.java:95)

        at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:545)

        at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256)

        at weblogic.work.ExecuteThread.run(ExecuteThread.java:221)

>

<Sep 8, 2015 11:47:36 PM PDT> <Error> <Kernel> <BEA-000802> <ExecuteRequest failed

java.lang.OutOfMemoryError: getNewTla.

  1. java.lang.OutOfMemoryError: getNewTla

        at com.sun.jmx.remote.internal.ArrayNotificationBuffer.fetchNotifications(ArrayNotificationBuffer.java:459)

        at com.sun.jmx.remote.internal.ArrayNotificationBuffer$ShareBuffer.fetchNotifications(ArrayNotificationBuffer.java:209)

        at com.sun.jmx.remote.internal.ServerNotifForwarder.fetchNotifs(ServerNotifForwarder.java:258)

        at javax.management.remote.rmi.RMIConnectionImpl$2.run(RMIConnectionImpl.java:1227)

        at javax.management.remote.rmi.RMIConnectionImpl$2.run(RMIConnectionImpl.java:1225)

        Truncated. see log file for complete stacktrace

>

<Sep 8, 2015 11:47:37 PM PDT> <Error> <EJB> <BEA-010079> <An error occurred while attempting to receive a message from JMS for processing by a message-driven bean: oracle.jms.AQjmsException: JMS-120: Dequeue failed

Nested exception: java.sql.SQLException: Protocol violation: [1]

The exception is : oracle.jms.AQjmsException: JMS-120: Dequeue failed

        at oracle.jms.AQjmsError.throwEx(AQjmsError.java:315)

        at oracle.jms.AQjmsConsumer.jdbcDequeue(AQjmsConsumer.java:1620)

        at oracle.jms.AQjmsConsumer.receiveFromAQ(AQjmsConsumer.java:1035)

        at oracle.jms.AQjmsConsumer.receiveFromAQ(AQjmsConsumer.java:960)

        at oracle.jms.AQjmsConsumer.receiveFromAQ(AQjmsConsumer.java:938)

        at oracle.jms.AQjmsConsumer.receive(AQjmsConsumer.java:790)

        at weblogic.ejb.container.internal.NewJMSMessagePoller$1.run(NewJMSMessagePoller.java:264)

        at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)

        at weblogic.ejb.container.internal.JMSConnectionPoller.doPrivilegedJMSAction(JMSConnectionPoller.java:2752)

        at weblogic.ejb.container.internal.NewJMSMessagePoller.processOneMessage(NewJMSMessagePoller.java:260)

        at weblogic.ejb.container.internal.NewJMSMessagePoller.run(NewJMSMessagePoller.java:120)

        at weblogic.ejb.container.internal.NewJMSMessagePoller.timerExpired(NewJMSMessagePoller.java:236)

        at weblogic.timers.internal.TimerImpl.run(TimerImpl.java:273)

        at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:545)

        at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256)

        at weblogic.work.ExecuteThread.run(ExecuteThread.java:221)

Caused by: java.sql.SQLException: Protocol violation: [1]

        at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:502)

        at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:205)

        at oracle.jdbc.driver.T4Caqdq.doOAQDQ(T4Caqdq.java:183)

        at oracle.jdbc.driver.T4CConnection.doDequeue(T4CConnection.java:4711)

        at oracle.jdbc.driver.PhysicalConnection.dequeue(PhysicalConnection.java:17863)

        at oracle.jdbc.driver.PhysicalConnection.dequeue(PhysicalConnection.java:17949)

        at weblogic.jdbc.wrapper.PoolConnection_oracle_jdbc_driver_T4CConnection.dequeue(Unknown Source)

        at oracle.jms.AQjmsConsumer.jdbcConnectionDequeueCheck25242(AQjmsConsumer.java:1713)

        at oracle.jms.AQjmsConsumer.jdbcDequeue(AQjmsConsumer.java:1295)

        at oracle.jms.AQjmsConsumer.receiveFromAQ(AQjmsConsumer.java:1035)

        at oracle.jms.AQjmsConsumer.receiveFromAQ(AQjmsConsumer.java:960)

        at oracle.jms.AQjmsConsumer.receiveFromAQ(AQjmsConsumer.java:938)

        at oracle.jms.AQjmsConsumer.receive(AQjmsConsumer.java:790)

        at weblogic.ejb.container.internal.NewJMSMessagePoller$1.run(NewJMSMessagePoller.java:264)

        at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)

        at weblogic.ejb.container.internal.JMSConnectionPoller.doPrivilegedJMSAction(JMSConnectionPoller.java:2752)

        at weblogic.ejb.container.internal.NewJMSMessagePoller.processOneMessage(NewJMSMessagePoller.java:260)

        at weblogic.ejb.container.internal.NewJMSMessagePoller.run(NewJMSMessagePoller.java:120)

        at weblogic.ejb.container.internal.NewJMSMessagePoller.timerExpired(NewJMSMessagePoller.java:235)

        ... 4 more

>

<Sep 8, 2015 11:47:37 PM PDT> <Error> <EJB> <BEA-010079> <An error occurred while attempting to receive a message from JMS for processing by a message-driven bean: oracle.jms.AQjmsException: JMS-120: Dequeue failed

Nested exception: java.sql.SQLException: Protocol violation: [1]

The exception is : oracle.jms.AQjmsException: JMS-120: Dequeue failed

        at oracle.jms.AQjmsError.throwEx(AQjmsError.java:315)

        at oracle.jms.AQjmsConsumer.jdbcDequeue(AQjmsConsumer.java:1620)

        at oracle.jms.AQjmsConsumer.receiveFromAQ(AQjmsConsumer.java:1035)

        at oracle.jms.AQjmsConsumer.receiveFromAQ(AQjmsConsumer.java:960)

        at oracle.jms.AQjmsConsumer.receiveFromAQ(AQjmsConsumer.java:938)

        at oracle.jms.AQjmsConsumer.receive(AQjmsConsumer.java:790)

        at weblogic.ejb.container.internal.NewJMSMessagePoller$1.run(NewJMSMessagePoller.java:264)

        at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)

        at weblogic.ejb.container.internal.JMSConnectionPoller.doPrivilegedJMSAction(JMSConnectionPoller.java:2752)

        at weblogic.ejb.container.internal.NewJMSMessagePoller.processOneMessage(NewJMSMessagePoller.java:260)

        at weblogic.ejb.container.internal.NewJMSMessagePoller.run(NewJMSMessagePoller.java:120)

        at weblogic.ejb.container.internal.NewJMSMessagePoller.timerExpired(NewJMSMessagePoller.java:236)

        at weblogic.timers.internal.TimerImpl.run(TimerImpl.java:273)

        at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:545)

        at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256)

        at weblogic.work.ExecuteThread.run(ExecuteThread.java:221)

Caused by: java.sql.SQLException: Protocol violation: [1]

        at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:502)

        at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:205)

        at oracle.jdbc.driver.T4Caqdq.doOAQDQ(T4Caqdq.java:183)

        at oracle.jdbc.driver.T4CConnection.doDequeue(T4CConnection.java:4711)

        at oracle.jdbc.driver.PhysicalConnection.dequeue(PhysicalConnection.java:17863)

        at oracle.jdbc.driver.PhysicalConnection.dequeue(PhysicalConnection.java:17949)

        at weblogic.jdbc.wrapper.PoolConnection_oracle_jdbc_driver_T4CConnection.dequeue(Unknown Source)

        at oracle.jms.AQjmsConsumer.jdbcConnectionDequeueCheck25242(AQjmsConsumer.java:1713)

        at oracle.jms.AQjmsConsumer.jdbcDequeue(AQjmsConsumer.java:1295)

        at oracle.jms.AQjmsConsumer.receiveFromAQ(AQjmsConsumer.java:1035)

        at oracle.jms.AQjmsConsumer.receiveFromAQ(AQjmsConsumer.java:960)

        at oracle.jms.AQjmsConsumer.receiveFromAQ(AQjmsConsumer.java:938)

        at oracle.jms.AQjmsConsumer.receive(AQjmsConsumer.java:790)

        at weblogic.ejb.container.internal.NewJMSMessagePoller$1.run(NewJMSMessagePoller.java:264)

        at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)

        at weblogic.ejb.container.internal.JMSConnectionPoller.doPrivilegedJMSAction(JMSConnectionPoller.java:2752)

        at weblogic.ejb.container.internal.NewJMSMessagePoller.processOneMessage(NewJMSMessagePoller.java:260)

        at weblogic.ejb.container.internal.NewJMSMessagePoller.run(NewJMSMessagePoller.java:120)

        at weblogic.ejb.container.internal.NewJMSMessagePoller.timerExpired(NewJMSMessagePoller.java:235)

        ... 4 more

>

<Sep 8, 2015 11:47:37 PM PDT> <Error> <EJB> <BEA-010079> <An error occurred while attempting to receive a message from JMS for processing by a message-driven bean: oracle.jms.AQjmsException: JMS-120: Dequeue failed

Sep 8, 2015 11:49:19 PM PDT> <Warning> <oracle.portlet.client.service.pipeline.TimeoutMonitor> <WCS-40025> <Muffling exception in method TimeoutMonitor$1.run, context = Throwable: java.lang.OutOfMemoryError: getNewTla.>

<Sep 8, 2015 11:49:18 PM PDT> <Warning> <oracle.as.ess> <ESS-06002> <Failed to close runtime service handle. java.lang.OutOfMemoryError: getNewTla

  1. java.lang.OutOfMemoryError: getNewTla

        at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:511)

        at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:205)

        at oracle.jdbc.driver.T4C7Ocommoncall.doOROLLBACK(T4C7Ocommoncall.java:72)

        at oracle.jdbc.driver.T4CConnection.doRollback(T4CConnection.java:751)

        at oracle.jdbc.driver.PhysicalConnection.rollback(PhysicalConnection.java:5150)

        at weblogic.jdbc.wrapper.PoolConnection_oracle_jdbc_driver_T4CConnection.rollback(Unknown Source)

        at oracle.as.scheduler.runtime.jdbc.RuntimeBeanImpl.close(RuntimeBeanImpl.java:1410)

        at oracle.as.scheduler.runtime.RuntimeImpl.close(RuntimeImpl.java:642)

        at oracle.as.scheduler.runtime.RuntimeStore.close(RuntimeStore.java:240)

        at oracle.as.scheduler.adapter.ra.EventsWorker.waitForWorkNotification(EventsWorker.java:609)

        at oracle.as.scheduler.adapter.ra.EventsWorker.run(EventsWorker.java:411)

        at weblogic.connector.security.layer.WorkImpl.runIt(WorkImpl.java:108)

        at weblogic.connector.security.layer.WorkImpl.run(WorkImpl.java:44)

        at weblogic.connector.work.WorkRequest.run(WorkRequest.java:95)

        at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:545)

        at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256)

        at weblogic.work.ExecuteThread.run(ExecuteThread.java:221)

>

<Sep 8, 2015 11:49:20 PM PDT> <Error> <JDBC> <BEA-001112> <Test "SELECT 1 FROM DUAL" set up for pool "JRFWSAsyncDSAQ" failed with exception: "java.sql.SQLException: Protocol violation: [1]".>

<Sep 8, 2015 11:49:20 PM PDT> <Error> <JDBC> <BEA-001112> <Test "SELECT 1 FROM DUAL" set up for pool "JRFWSAsyncDSAQ" failed with exception: "java.sql.SQLException: Protocol violation: [1]".>

<Sep 8, 2015 11:49:20 PM PDT> <Error> <JDBC> <BEA-001112> <Test "SELECT 1 FROM DUAL" set up for pool "JRFWSAsyncDSAQ" failed with exception: "java.sql.SQLException: Protocol violation: [1]".>

Here is my jrocket setting

EXTRA_JAVA_PROPERTIES="-Dcommon.components.home=${COMMON_COMPONENTS_HOME} -Djrf.version=11.1.1  -Dorg.apache.commons.logging.Log=org.apache.commons.logging.impl.Jdk14Logger -Ddomain.home=${DOMAIN_HOME} -XXtlasize:min=8k,preferred=128k  -XX:+UnlockDiagnosticVMOptions  -XX:OptFile=${COMMON_COMPONENTS_HOME}/modules/oracle.jrf_11.1.1/jrocket_optfile.txt -Doracle.server.config.dir=${ORACLE_DOMAIN_CONFIG_DIR}/servers/${SERVER_NAME} -Doracle.domain.config.dir=${ORACLE_DOMAIN_CONFIG_DIR}  -Digf.arisidbeans.carmlloc=${ORACLE_DOMAIN_CONFIG_DIR}/carml  -Digf.arisidstack.home=${ORACLE_DOMAIN_CONFIG_DIR}/arisidprovider -Doracle.security.jps.config=${DOMAIN_HOME}/config/fmwconfig/jps-config.xml -Doracle.deployed.app.dir=${DOMAIN_HOME}/servers/${SERVER_NAME}/tmp/_WL_user -Doracle.deployed.app.ext=/- -Dweblogic.alternateTypesDirectory=${ALT_TYPES_DIR} -Djava.protocol.handler.pkgs=${PROTOCOL_HANDLERS}  ${WLS_JDBC_REMOTE_ENABLED} ${EXTRA_JAVA_PROPERTIES}"

any suggestion are appreciated. 

thanks.

Comments

Hilary Farrell-Oracle
Answer

Hi JKL,
If you haven't already done so, please refer to section 20.3 Controlling Access to Applications, Pages, and Page Components in our APEX 20.2 User's Guide. You haven't stated what Authentication Scheme has been selected for your app, so I'll go with the assumption that it's the default APEX Application Account. The usernames that you list in your Access Control list, should be created as new users in the workspace. Please refer to section 2.7 Managing Users in a Workspace in our APEX 20.2 Administration Guide, specifically section 2.7.3 Creating User Accounts. Once you've created the users in the workspace, to correspond with the user names you've defined in your app's Access Control list, then those user credentials can be used to log into the app.
I hope this helps.
Regards,
Hilary

Marked as Answer by JKL · Oct 27 2020
JKL

Hilary,
Thanks for the reply. I am comparing the user from the Application specific Users area in the Administration section and the APEX Workspace user. The two lists don't match. Attached please find the screen shots between the two. One from the Application Administration Access Control User list and the other is the Workspace user. I don't think that the two lists are the same like you suggested unless I misunderstand you. The following two screen shots will show you the difference. I blur the domain name for the email address. In the Workspace user section, you can ignore GETHELP as the user. That's for another app/login. But jlam@xxxxxx.com is my actual login to the apex.oracle.com. In the specific app, I also have an user named jlam@xxxxxx.com. I can understand this one. But I have also created ds9, jl2 via the Application Administration menu link area, i.e. default Access Control List feature Admin page seeded with the App Creation wizard. But I am not finding these users in the Workspace User list. So I don't think that the two are the same here.
The following screen shot was taken from the App Administration section of the User list.
apex_user_list_from_App-ACL.pngThe following screen shot was taken from the Workspace Manage User section.
apex_user_list_from_WrkspaceAdmin.png
The two are very different. My understanding is that the APEX user is created in the Workspace. But my question is related to the Application level user list. Where do they create and how can I login as those user such as DS9 in the screen. There is no place to create the password when you add a new user via the Application Administration section.
So are you suggesting that I have to also create the same user e.g. DS9 or JL2 in the Workspace area and then they can access the app that way?
Hope I can explain my question properly. Thanks

JKL

Hilary,
Ok, I just create new user via the Manage Workspace User area and it seems to work the way it is. But how does APEX reconcile the two lists. Are they truely the same user in this case other than the user name is the same. But it is just weird that this is the method. Why can't APEX simply actually create the Workspace user directly if the user is not already created? Either way, thanks for your reply.

Hilary Farrell-Oracle

Hi JKL,
So are you suggesting that I have to also create the same user e.g. DS9 or JL2 in the Workspace area and then they can access the app that way?
Yes, that's correct. When you're using APEX Accounts authentication, the users in question must exist in the workspace in order to have access to the application. Users added to the Access Control List via the Application Administration are not automatically created as workspace users. You must use the workspace Administration -> Manage Users and Groups -> Create User wizard in order to actually create the new users.
Regards,
Hilary

JKL

Hilary,
It would be nice to automatically add this as APEX user or take you to the add user page for the app if the app has a custom application user creation process. I guess that this may be quite a complicated feature. For now, thanks for your update.

1 - 5
Locked Post
New comments cannot be posted to this locked post.

Post Details

Locked on Dec 24 2015
Added on Sep 9 2015
#application-servers, #jrockit
1 comment
3,084 views