can we please conclude that Weblogic 10.3.x is not supported by Idea 10.5 ?

Hi,

After having spent a lot of time trying every possible option to deploy a simple war file from 10.5 to a weblogic 10.3.4 configuration, i can only conclude that this is just not working / supported in the Idea. Deploying to 9.2 works fine, none of the 10.3(.3 .4 .5) instances i tried work. The forum reveals that this is an ongoing issue for several years even.

So i was hoping if one of the devs can just confirm that this feature is currently broken. It would save people a lot of time.

Thanks
Jorg

PS Has any work being done in the EAP on this ?

8 comments

I've just tried WebLogic 10.3.5 in IDEA 10.5.2 and it seems to work: I've created a WebLogic Local run configuration, added a simple exploded war
artifact on 'Deployment' tab and pressed 'Run'.

Could you please provide a more detailed description of your problems?

--
Nikolay Chashnikov
Software Developer
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"

0

I have exactly this as well. A maven project with type=war in pom.xml. It is added in the deployment tab as exploded war. When i build the project and copy the exploded war from the target directory to weblogic autodeploy it works.

When weblogic is starting it says

<22-Nov-2011 12:47:22 o'clock CET> <Notice> <WebLogicServer> <BEA-000331> <Started WebLogic Admin Server "AdminServer" for domain "testmonitor_domain" running in Development Mode>
<22-Nov-2011 12:47:22 o'clock CET> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to RUNNING>
<22-Nov-2011 12:47:22 o'clock CET> <Notice> <WebLogicServer> <BEA-000360> <Server started in RUNNING mode>

and then nothing. In 9.2 you see after that last line always 'Connected to server' and then the deployment begins. I have tried everything, from local to remote server - exploded or packaged - different wls versions it just does not deploy anything. There are a few exceptions in idea.log, but they don't look related and do not happen after i press the start button

Caused by: java.lang.RuntimeException: org.sonatype.nexus.index.context.UnsupportedExistingLuceneIndexException: The existing index has no NexusIndexer descriptor
    at org.sonatype.nexus.index.context.DefaultIndexingContext.checkAndUpdateIndexDescriptor(DefaultIndexingContext.java:214)
    at org.sonatype.nexus.index.context.DefaultIndexingContext.prepareIndex(DefaultIndexingContext.java:174)
    at org.sonatype.nexus.index.context.DefaultIndexingContext.<init>(DefaultIndexingContext.java:132)
    at org.sonatype.nexus.index.DefaultNexusIndexer.addIndexingContext(DefaultNexusIndexer.java:78)
    at org.jetbrains.idea.maven.server.embedder.Maven2ServerIndexerImpl.createIndex(Maven2ServerIndexerImpl.java:80)
    at sun.reflect.GeneratedMethodAccessor2.invoke(Unknown Source)

2011-11-22 11:36:24,954 [71967098]   INFO -      #org.jetbrains.idea.maven - Failed to update Maven indices for: [central] http://repo1.maven.org/maven2
java.lang.RuntimeException: No available dir found
    at org.jetbrains.idea.maven.indices.MavenIndices.findAvailableDir(MavenIndices.java:115)
    at org.jetbrains.idea.maven.indices.MavenIndex.findAvailableDataDirName(MavenIndex.java:439)
    at org.jetbrains.idea.maven.indices.MavenIndex.updateData(MavenIndex.java:320)
    at org.jetbrains.idea.maven.indices.MavenIndex.updateOrRepair(MavenIndex.java:276)
    at org.jetbrains.idea.maven.indices.MavenIndices.updateOrRepair(MavenIndices.java:121)
    at org.jetbrains.idea.maven.indices.MavenIndicesManager.doUpdateIndices(MavenIndicesManager.java:267)

As most of the time, the weblogic logs are quite empty and useless.

I know weblogic quite well, so maybe it would help if you tell me a bit more about the actual mechanics of deploying to wls from idea ? How does it happen, through WLST ?

Jorg

PS i just tried the latest EAP as well, the problem persists

0
Hello,



IDEA utilizes JMX protocol to manage WebLogic instances, similar to as described in
http://download.oracle.com/docs/cd/E13222_01/wls/docs90/jmx/accessWLS.html

Absence of the 'Connected to server' on the IDEA server console marks there are some connection problems.
You may try to find what sort of in the following way:

1) add the following content:

<category name="#com.intellij.javaee.weblogic.runDebug.weblogicServerInstances.version9.Weblogic9AbstractInstance">
    <priority value="DEBUG"/> <appender-ref ref="CONSOLE-ALL"/>
   </category>

into the <IDEA home>/bin/log.xml right before <root> node at the end, so the end of file should look like:

...
  <category name="#com.intellij.javaee.weblogic.runDebug.weblogicServerInstances.version9.Weblogic9AbstractInstance">
    <priority value="DEBUG"/> <appender-ref ref="CONSOLE-ALL"/>
   </category>
  <root>
    <priority value="INFO"/>
    <appender-ref ref="DIALOG"/>
     <appender-ref ref="CONSOLE-WARN"/>    <!--  $COMMENT_LINE_FOR_TEST_MODE$ If a line contains such macro, it will be  deleted then we start IDEA in JUnit Test mode -->
     <appender-ref ref="FILE"/>
  </root>
</log4j:configuration>

2) restart IDEA if it was started already

3) start WebLogic IDEA run configuration and wait until it is fully started

4) check IDEA log (<user home>/.IntelliJIdea10/system/log/idea.log) for relevant entries


Even in case of successful connection, you may see some entries like

[  44736]  DEBUG - ion9.Weblogic9AbstractInstance -  
java.io.IOException
...<several caused-by>...
Caused by: java.rmi.ConnectException: Destination unreachable; nested exception is:
java.net.ConnectException: Connection refused: connect; No available router to destination
...
which are written into the log while server is starting


Regards,
Michael
0

Thanks for your help Michael. With your help i could establish from the logs that somehow the JMX port in the domain was being blocked from access by our SSO authenticator library. It would be extremely helpful to display this stacktrace in the console so that people don't wonder what is going on.

I apologize for taking the wrong conclusion initially, but i had no other information to conclude otherwise.

2011-11-24 11:18:22,699 [10776962]  DEBUG - ion9.Weblogic9AbstractInstance -  
java.io.IOException
    at weblogic.management.remote.common.ClientProviderBase.makeConnection(ClientProviderBase.java:196)
    at weblogic.management.remote.common.ClientProviderBase.newJMXConnector(ClientProviderBase.java:84)
    at javax.management.remote.JMXConnectorFactory.newJMXConnector(JMXConnectorFactory.java:338)
    at javax.management.remote.JMXConnectorFactory.connect(JMXConnectorFactory.java:247)
    at com.intellij.javaee.weblogic.runDebug.weblogicServerInstances.version9.WeblogicJMXConnector.connect(WeblogicJMXConnector.java:51)
    at com.intellij.javaee.weblogic.runDebug.weblogicServerInstances.version9.Weblogic9AbstractInstance.connect(Weblogic9AbstractInstance.java:140)
    at com.intellij.javaee.weblogic.runDebug.weblogicServerInstances.version9.Weblogic9AbstractInstance.initConnection(Weblogic9AbstractInstance.java:129)
    at com.intellij.javaee.weblogic.runDebug.weblogicServerInstances.version9.Weblogic9AbstractInstance.refreshStateImpl(Weblogic9AbstractInstance.java:420)
    at com.intellij.javaee.weblogic.runDebug.weblogicServerInstances.version9.ServerPollThreadForWL9.refreshState(ServerPollThreadForWL9.java:34)
    at com.intellij.javaee.weblogic.runDebug.weblogicServerInstances.WeblogicAbstractInstance.refreshState(WeblogicAbstractInstance.java:283)
    at com.intellij.javaee.weblogic.runDebug.weblogicServerInstances.version9.Weblogic9LocalInstance.access$000(Weblogic9LocalInstance.java:18)
    at com.intellij.javaee.weblogic.runDebug.weblogicServerInstances.version9.Weblogic9LocalInstance$1.run(Weblogic9LocalInstance.java:54)
    at com.intellij.javaee.weblogic.runDebug.weblogicServerInstances.version9.ServerPollThreadForWL9.runRequest(ServerPollThreadForWL9.java:27)
    at com.intellij.javaee.weblogic.runDebug.weblogicServerInstances.ServerPollThread.runImmediately(ServerPollThread.java:110)
    at com.intellij.javaee.weblogic.runDebug.weblogicServerInstances.ServerPollThread.run(ServerPollThread.java:163)
    at com.intellij.openapi.application.impl.ApplicationImpl$7.run(ApplicationImpl.java:386)
    at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
    at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
    at java.util.concurrent.FutureTask.run(FutureTask.java:138)
    at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
    at java.lang.Thread.run(Thread.java:619)
    at com.intellij.openapi.application.impl.ApplicationImpl$1$1.run(ApplicationImpl.java:130)
Caused by: javax.naming.CommunicationException [Root exception is java.net.ConnectException: t3://localhost:7001: Destination unreachable; nested exception is:
    java.net.ConnectException: Connection refused: connect; No available router to destination]
    at weblogic.jndi.internal.ExceptionTranslator.toNamingException(ExceptionTranslator.java:40)
    at weblogic.jndi.WLInitialContextFactoryDelegate.toNamingException(WLInitialContextFactoryDelegate.java:788)
    at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:366)
    at weblogic.jndi.Environment.getContext(Environment.java:315)
    at weblogic.jndi.Environment.getContext(Environment.java:285)
    at weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFactory.java:117)
    at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:667)
    at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:288)
    at javax.naming.InitialContext.init(InitialContext.java:223)
    at javax.naming.InitialContext.<init>(InitialContext.java:197)
    at weblogic.management.remote.common.ClientProviderBase.makeConnection(ClientProviderBase.java:178)
    ... 22 more
Caused by: java.net.ConnectException: t3://localhost:7001: Destination unreachable; nested exception is:
    java.net.ConnectException: Connection refused: connect; No available router to destination
    at weblogic.rjvm.RJVMFinder.findOrCreateInternal(RJVMFinder.java:216)
    at weblogic.rjvm.RJVMFinder.findOrCreate(RJVMFinder.java:170)
    at weblogic.rjvm.ServerURL.findOrCreateRJVM(ServerURL.java:153)
    at weblogic.jndi.WLInitialContextFactoryDelegate$1.run(WLInitialContextFactoryDelegate.java:345)
    at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
    at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:146)
    at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:340)
    ... 30 more
Caused by: java.rmi.ConnectException: Destination unreachable; nested exception is:
    java.net.ConnectException: Connection refused: connect; No available router to destination
    at weblogic.rjvm.ConnectionManager.bootstrap(ConnectionManager.java:470)
    at weblogic.rjvm.ConnectionManager.bootstrap(ConnectionManager.java:321)
    at weblogic.rjvm.RJVMManager.findOrCreateRemoteInternal(RJVMManager.java:254)
    at weblogic.rjvm.RJVMManager.findOrCreate(RJVMManager.java:197)
    at weblogic.rjvm.RJVMFinder.findOrCreateRemoteServer(RJVMFinder.java:238)
    at weblogic.rjvm.RJVMFinder.findOrCreateInternal(RJVMFinder.java:200)
    ... 36 more

0

So it does seem that there is an issue of some sort. The stacktrace i posted in my previous message actually appears every time i deploy to WLS and it seems harmless. However occasionally during development idea is no longer able to deploy to Weblogic and then only a restart of the ide will fix it. When this happens i get below stacktrace in the logs, repeated many times:

2011-11-25 10:28:06,377 [1771597]  DEBUG - ion9.Weblogic9AbstractInstance -  
java.io.IOException
    at weblogic.management.remote.common.ClientProviderBase.makeConnection(ClientProviderBase.java:196)
    at weblogic.management.remote.common.ClientProviderBase.newJMXConnector(ClientProviderBase.java:84)
    at javax.management.remote.JMXConnectorFactory.newJMXConnector(JMXConnectorFactory.java:338)
    at javax.management.remote.JMXConnectorFactory.connect(JMXConnectorFactory.java:247)
    at com.intellij.javaee.weblogic.runDebug.weblogicServerInstances.version9.WeblogicJMXConnector.connect(WeblogicJMXConnector.java:51)
    at com.intellij.javaee.weblogic.runDebug.weblogicServerInstances.version9.Weblogic9AbstractInstance.connect(Weblogic9AbstractInstance.java:140)
    at com.intellij.javaee.weblogic.runDebug.weblogicServerInstances.version9.Weblogic9AbstractInstance.initConnection(Weblogic9AbstractInstance.java:129)
    at com.intellij.javaee.weblogic.runDebug.weblogicServerInstances.version9.Weblogic9AbstractInstance.refreshStateImpl(Weblogic9AbstractInstance.java:420)
    at com.intellij.javaee.weblogic.runDebug.weblogicServerInstances.version9.ServerPollThreadForWL9.refreshState(ServerPollThreadForWL9.java:34)
    at com.intellij.javaee.weblogic.runDebug.weblogicServerInstances.ServerPollThread.pollServer(ServerPollThread.java:216)
    at com.intellij.javaee.weblogic.runDebug.weblogicServerInstances.ServerPollThread.access$000(ServerPollThread.java:34)
    at com.intellij.javaee.weblogic.runDebug.weblogicServerInstances.ServerPollThread$1.run(ServerPollThread.java:51)
    at com.intellij.javaee.weblogic.runDebug.weblogicServerInstances.version9.ServerPollThreadForWL9.runRequest(ServerPollThreadForWL9.java:27)
    at com.intellij.javaee.weblogic.runDebug.weblogicServerInstances.ServerPollThread.runImmediately(ServerPollThread.java:110)
    at com.intellij.javaee.weblogic.runDebug.weblogicServerInstances.ServerPollThread.run(ServerPollThread.java:163)
    at com.intellij.openapi.application.impl.ApplicationImpl$7.run(ApplicationImpl.java:386)
    at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
    at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
    at java.util.concurrent.FutureTask.run(FutureTask.java:138)
    at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
    at java.lang.Thread.run(Thread.java:619)
    at com.intellij.openapi.application.impl.ApplicationImpl$1$1.run(ApplicationImpl.java:130)
Caused by: javax.naming.CommunicationException [Root exception is java.net.ConnectException: t3://localhost:7001: Destination unreachable; nested exception is:
    java.net.ProtocolException: unrecognized response from proxy: 'HTTP/1.0 403 Forbidden'; No available router to destination]
    at weblogic.jndi.internal.ExceptionTranslator.toNamingException(ExceptionTranslator.java:40)
    at weblogic.jndi.WLInitialContextFactoryDelegate.toNamingException(WLInitialContextFactoryDelegate.java:788)
    at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:366)
    at weblogic.jndi.Environment.getContext(Environment.java:315)
    at weblogic.jndi.Environment.getContext(Environment.java:285)
    at weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFactory.java:117)
    at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:667)
    at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:288)
    at javax.naming.InitialContext.init(InitialContext.java:223)
    at javax.naming.InitialContext.<init>(InitialContext.java:197)
    at weblogic.management.remote.common.ClientProviderBase.makeConnection(ClientProviderBase.java:178)
    ... 22 more
Caused by: java.net.ConnectException: t3://localhost:7001: Destination unreachable; nested exception is:
    java.net.ProtocolException: unrecognized response from proxy: 'HTTP/1.0 403 Forbidden'; No available router to destination
    at weblogic.rjvm.RJVMFinder.findOrCreateInternal(RJVMFinder.java:216)
    at weblogic.rjvm.RJVMFinder.findOrCreate(RJVMFinder.java:170)
    at weblogic.rjvm.ServerURL.findOrCreateRJVM(ServerURL.java:153)
    at weblogic.jndi.WLInitialContextFactoryDelegate$1.run(WLInitialContextFactoryDelegate.java:345)
    at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
    at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:146)
    at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:340)
    ... 30 more
Caused by: java.rmi.ConnectException: Destination unreachable; nested exception is:
    java.net.ProtocolException: unrecognized response from proxy: 'HTTP/1.0 403 Forbidden'; No available router to destination
    at weblogic.rjvm.ConnectionManager.bootstrap(ConnectionManager.java:470)
    at weblogic.rjvm.ConnectionManager.bootstrap(ConnectionManager.java:321)
    at weblogic.rjvm.RJVMManager.findOrCreateRemoteInternal(RJVMManager.java:254)
    at weblogic.rjvm.RJVMManager.findOrCreate(RJVMManager.java:197)
    at weblogic.rjvm.RJVMFinder.findOrCreateRemoteServer(RJVMFinder.java:238)
    at weblogic.rjvm.RJVMFinder.findOrCreateInternal(RJVMFinder.java:200)

Note that both this one and the previous stacktrace are ConnectExceptions, but this one says java.net.ProtocolException: unrecognized response from proxy: 'HTTP/1.0 403 Forbidden'; No available router to destination] whereas the harmless one says java.net.ConnectException: Connection refused: connect; No available router to destination

I hope this helps the dev team in troubleshooting this. For now restarting the ide  seems to have worked every time. I also don't know what triggers the behaviour to change, seems fairly random.

0

Hello,

The last exception with java.net.ProtocolException: unrecognized response from proxy: 'HTTP/1.0 403 Forbidden'; No available router to destination]

in the stacktrace looks like caused by your  proxy.
I suspect the proxy may cache the error response during the IDEA  session, and clear the cache on IDEA restart.

I would recommend not to use a proxy if possible, or try to tune it not to cache the error response.
I can see similar issue with WebLogic over the web: https://forums.oracle.com/forums/thread.jspa?threadID=2294744


Regards,
Michael
0

ok i've disabled the http proxy in IDEA, i'll report back in a few days hopefully with the good news that it fixes the 'issue'.

0

good news, this seems to get rid of any deployment issues. Works 100% of the time now. So if you're seeing this behaviour try disabling your configured http proxy settings it might solve your case !

0

Please sign in to leave a comment.