Skip to Main Content
Forums

SQL Developer

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!

SQL Developer 17.4.1.054.0712 unable to run

Jojo G-OracleMar 27 2018 — edited Mar 27 2018

I am trying to download as  use SQL Developer 17.4.1.054.0712 . I tried  both version with JDK included and with out it .

When I unzip and  try to run , it results in an exception. 

java.lang.Exception: Stack trace

        at java.lang.Thread.dumpStack(Thread.java:1329)

        at oracle.ideimpl.MainWindowImpl.<init>(MainWindowImpl.java:166)

        at oracle.ide.osgi.Activator.setupWindow(Activator.java:307)

        at oracle.ide.osgi.Activator.start(Activator.java:139)

        at org.eclipse.osgi.framework.internal.core.BundleContextImpl$1.run(Bund

leContextImpl.java:711)

        at java.security.AccessController.doPrivileged(Native Method)

        at org.eclipse.osgi.framework.internal.core.BundleContextImpl.startActiv

ator(BundleContextImpl.java:702)

        at org.eclipse.osgi.framework.internal.core.BundleContextImpl.start(Bund

leContextImpl.java:683)

        at org.eclipse.osgi.framework.internal.core.BundleHost.startWorker(Bundl

eHost.java:381)

        at org.eclipse.osgi.framework.internal.core.AbstractBundle.resume(Abstra

ctBundle.java:390)

        at org.eclipse.osgi.framework.internal.core.Framework.resumeBundle(Frame

work.java:1184)

        at org.eclipse.osgi.framework.internal.core.StartLevelManager.resumeBund

les(StartLevelManager.java:559)

        at org.eclipse.osgi.framework.internal.core.StartLevelManager.resumeBund

les(StartLevelManager.java:544)

        at org.eclipse.osgi.framework.internal.core.StartLevelManager.incFWSL(St

artLevelManager.java:457)

        at org.eclipse.osgi.framework.internal.core.StartLevelManager.doSetStart

Level(StartLevelManager.java:243)

        at org.eclipse.osgi.framework.internal.core.EquinoxLauncher.internalStar

t(EquinoxLauncher.java:271)

        at org.eclipse.osgi.framework.internal.core.EquinoxLauncher.start(Equino

xLauncher.java:241)

        at org.eclipse.osgi.launch.Equinox.start(Equinox.java:258)

        at org.netbeans.core.netigso.Netigso.start(Netigso.java:191)

        at org.netbeans.NetigsoHandle.startFramework(NetigsoHandle.java:209)

        at org.netbeans.ModuleManager.enable(ModuleManager.java:1366)

        at org.netbeans.ModuleManager.enable(ModuleManager.java:1170)

        at org.netbeans.core.startup.ModuleList.installNew(ModuleList.java:340)

        at org.netbeans.core.startup.ModuleList.trigger(ModuleList.java:276)

        at org.netbeans.core.startup.ModuleSystem.restore(ModuleSystem.java:301)

        at org.netbeans.core.startup.Main.getModuleSystem(Main.java:181)

        at org.netbeans.core.startup.Main.getModuleSystem(Main.java:150)

        at org.netbeans.core.startup.Main.start(Main.java:307)

        at org.netbeans.core.startup.TopThreadGroup.run(TopThreadGroup.java:123)

        at java.lang.Thread.run(Thread.java:745)

Comments

Nigel Deakin-Oracle
The JMS specification doesn't offer a way to explicitly purge a destination (delete all its messages), though your chosen JMS provider might off a non-standard way of doing this.

You could of course simply consume all the messages in a loop.

If you want to use message expiration, don't try using setJMSExpiration on the Message. That method is not for the purpose you might think (see the javadocs). Instead use one of the following methods on MessageProducer:

void setTimeToLive(long timeToLive)
Sets the default length of time in milliseconds from its dispatch time that a produced message should be retained by the message system.

void send(Destination destination, Message message, int deliveryMode, int priority, long timeToLive)
Sends a message to a destination for an unidentified message producer, specifying delivery mode, priority and time to live.

timeToLive is in milliseconds.

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

Post Details

Locked on Apr 24 2018
Added on Mar 27 2018
#sql-developer
1 comment
621 views