It gives me the following exception message as I am trying to deploy an application.
BUILD FAILED
C:\eclipse\workspace\SLGIADMIN\build.xml:14: The following error occurred while executing this line:
C:\eclipse\buildcommon.xml:243: weblogic.Deployer$DeployerException: weblogic.deploy.api.tools.deployer.DeployerException: Unable to connect to 't3://localhost:7001': invalid type code: 31. Ensure the url represents a running admin server and that the credentials are correct. If using http protocol, tunneling must be enabled on the admin server.
I am using ant build in Eclipse and deploying to Weblogic 9.2.
I have been trying to find solution online. I have tried enable the tunneling in the Weblogic console. Doesn't work.
I have seen people mention we can use JDK 1.5 which will turn on tunneling on deploying. I have verified mine version is 1.5 too. I have ensured that too but did not fix the issue.
Invalid type code 31 is always because you're connecting with a different version of Java than what the server is running. Weblogic 9.2 only supports Java 1.5. Make sure that's what your ant task is using. You can also connect with later versions of Java if you set the following property in your client:
-Dsun.lang.ClassLoader.allowArraySyntax=true
Related
I have been trying to create my first RESTful execrcise using. But I am unable to deploy module due to error "com.sun.appserv.connectors.internal.api.ConnectorRuntimeException: Invalid resource : jdbc/playerDB__pm"
I checked and I have JNDI, daata source created.
Unlike specified in link. I am using:
-Netbeans 8.0.3, Java EE 7, GlassFish Server 4.
Also I have checked GlassFish is running fine.
Edit 1:
I have re-checked my 'Services' tab, and I could not find jdbc/__playedDB ,even though I have created it.
Its a bug, the JDBC resource file is not being created (atleast with versions I am using: GlassFish 4.1, Netbeans 8.0.2). Using GlassFish manually create.
There could still be different error untill you set following connectins:
database(data source) <- connection pool <- JNDI.
I'm working with IBM MobileFirst 7.1, and trying to get integration for ISAM working. So far I've been working with the sample application provided here, but I'm having issues with it when working with 7.1 MobileFirst client-side tools.
If I download and unzip the v3.5 integration package, and unzip the ISAMforMobileFirst test project, and I build it with the v7.0 CLI, it builds successfully. However, if I build it with the v7.1 CLI, I get an error like this:
Migrating project from version 7.0.0.00.20150211-0917 to version 7.1.0.00.20150807-0630.
[Error:
BUILD FAILED
/Applications/IBM/MobileFirst-CLI-7.1/mobilefirst-cli/node_modules/generator-worklight-server/lib/build.xml:497: com.worklight.upgrader.UpgradeEngineException: FWLPL0019E: Migrating the ISAMforMobileFirst project from version 7.0.0.00.20150211-0917 to version 7.1.0.00.20150807-0630 has failed because Cannot parse /Users/ferriera/Downloads/AmWorklightAdapter-3.5/sample/ISAMforMobileFirst/server/conf/authenticationConfig.xml
at com.worklight.upgrader.WLUpgradeEngine.upgradeProject(WLUpgradeEngine.java:271)
at com.worklight.upgrader.ant.UpgraderTask.execute(UpgraderTask.java:100)
at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:292)
at sun.reflect.GeneratedMethodAccessor4.invoke(Unknown Source)
A colleague also sees this exact error in MobileFirst Studio 7.1 (in Eclipse) so I'm guessing it's not a CLI-specific error.
I would assume that support for something has changed in authenticationConfig.xml in 7.1, and this hasn't been reflected in the migrator.
A few questions:
Is ISAM integration supported in 7.1?
Whilst I realise the sample application isn't technically supported in 7.1, if/since ISAM integration is, in theory it should be feasible to make it work. What's changed in authenticationConfig.xml syntax?
Edit: looks like the failure happens due to the following: <parameter name="embedded-pki-bridge-ca-p12-file-path" value="<file-path>"/> and more specifically: <file-path>.
Change it to the actual file path, and it will not fail importing.
Nothing in the authenticationConfig.xml file is about ISAM really; it's all declarations of realms, login modules, security tests...
There is a clear failure, and a PMR should be opened.
As for a local workaround, I've attempted to remove segments in the file that I thought might trigger it, but did not succeed to find a pattern that causes it...
I have been trying to setup eclipse with marklogic to use it as my xquery editor. I am following this link as per Marklogic: http://developer.marklogic.com/learn/xqdt-setup.
I did all the steps multiple times but I always get this error while run my default.xqy file:
Execution failed: java.lang.IllegalStateException: No content-type header in part.
Steps:
Installed MLC,
Installed Eclipse Helios 3.6.2
Configured XDBC server from admin console and use port as 8025.
In Eclipse, URL used for XCC: xcc://localhost:8025
I'm getting the following error while trying to access the Worklight server deployed in my machine:
Error 500: Worklight Console initialization failed.Logged Exception:
java.lang.RuntimeException: FWLSE0206E: The project /worklight failed to initialize, because the project database schema for data source jdbc:db2://xxxxx:50000/WRKLGHT is from version N/A, which is not supported by the server from version 6.1.0.00.20131126-0630. Use the Worklight ant tasks to upgrade the project database schema. [project worklight]
Follow what the error message suggests.
Make sure that the database schema you use for your DB2 database is one that fits Worklight 6.1
Upgrading from a previous version
How to manually update the database
How to configure the database using Ant
Make sure that you have properly configured your application server for working with DB2
Also make sure that you have properly set up DB2...
I have installed the latest version on the Sonar Eclipse Plugin on an Eclipse Juno 3.8. I am desperatly trying to connect the plugin to our running instance of Sonar. I'm behind a NTLM v2 Proxy. Hereunder, details of my configuration and my attempts.
Versions of products :
Eclipse 3.8,
Sonar Eclipse Plugin (Java Analyzer & m2e Connector) 3.2.0.20130627-1142-RELEASE,
SonarQube Server 3.7 (running on http://source01:9000, in the LAN, not behind the proxy, direct connection possible).
Trying to access with the following proxy configurations with an without http_proxy variable in the configuration:
direct with http_proxy : failure,
direct without http_proxy : success (but unable to use other Eclipse feature accessing Internet like the Marketplace),
native (with or without http_proxy) : failure,
manual (with or without http_proxy): failure.
I systematically got org.apache.http.conn.ConnectTimeoutException in the logs (trying to access http://source01:9000/api/authentication/validate which work in a browser).
No more idea on what to test.
I have finally found the problem seeking for a different one (Tomcat WST server started but Eclipse was unable to connect to it and timed out).
The problem comes from a strange and unpredictable behavior of the SOCKS proxy parameter.
When SOCKS proxy is defined, in some undefined cases, both starting a WST server or connecting to a SonarQube server through the plugin fail, whereas other functions like plugin installs work like a charm.
The solution came from https://stackoverflow.com/a/6459816/256561 and is to clear SOCKS proxy settings.