[JBoss JIRA] (JBIDE-21897) NullPointerException when creating an hbm.xml file
by Mohammed El Kihal (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21897?page=com.atlassian.jira.plugi... ]
Mohammed El Kihal commented on JBIDE-21897:
-------------------------------------------
I've tried with the latest 4.3.x.Nightly as suggested,still same issue.
> NullPointerException when creating an hbm.xml file
> --------------------------------------------------
>
> Key: JBIDE-21897
> URL: https://issues.jboss.org/browse/JBIDE-21897
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: hibernate
> Affects Versions: 4.3.0.Final
> Environment: eclipse.buildId=4.5.2.M20160212-1500
> java.version=1.8.0_73
> java.vendor=Oracle Corporation
> BootLoader constants: OS=win32, ARCH=x86_64, WS=win32, NL=en_US
> Framework arguments: -product org.eclipse.epp.package.jee.product
> Command-line arguments: -os win32 -ws win32 -arch x86_64 -product org.eclipse.epp.package.jee.product
> Reporter: Mohammed El Kihal
> Assignee: Koen Aers
> Priority: Blocker
> Attachments: HibernateError.txt, pom.xml
>
>
> Generating new Hibernate mapping files becomes impossible when converting a dynamic web project to maven and modifying the pom.xml.
> After switching the default pom.xml with the one i have pre-configured,it lead to the NPE,even after switching to the default one again,the error persisted.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-21857) Hot class reload doesn't work on OpenShift
by Thomas Mäder (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21857?page=com.atlassian.jira.plugi... ]
Thomas Mäder commented on JBIDE-21857:
--------------------------------------
[~rob.stryker] in org.eclipse.jdt.internal.debug.core.hcr.JavaHotCodeReplaceManager#getTypesToBytes (called from redefineTypesJDK).
> Hot class reload doesn't work on OpenShift
> ------------------------------------------
>
> Key: JBIDE-21857
> URL: https://issues.jboss.org/browse/JBIDE-21857
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.Beta2
> Reporter: Fred Bricon
> Assignee: Thomas Mäder
> Priority: Blocker
> Fix For: 4.3.1.CR1
>
>
> When enabling debug mode on an EAP server deployed on OpenShift, locally changing a class file will :
> - work sometimes when only the content of the method changed, but could fail in some other occasions with the Debugger saying the JDK is out of sync
> - will always fail if a method signature changed, the debugger saying JDK is out of sync
> Restarting the deployed module (with the .dodeploy flag) doesn't fixes the issue (as opposed to the same tweak ahen running on a local EAP server)
> This may be caused by running OpenJDK? Does it support the same level of debugging as Oracle JDK?
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-21845) Docker connection does not work with CDK build 2016-03-09
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21845?page=com.atlassian.jira.plugi... ]
Fred Bricon resolved JBIDE-21845.
---------------------------------
Resolution: Done
Resolved upstream
> Docker connection does not work with CDK build 2016-03-09
> ---------------------------------------------------------
>
> Key: JBIDE-21845
> URL: https://issues.jboss.org/browse/JBIDE-21845
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdk, upstream
> Affects Versions: 4.3.1.CR1
> Reporter: Martin Malina
> Assignee: Hardy Ferentschik
> Priority: Blocker
> Fix For: 4.3.1.CR1
>
>
> Today I tried cdk build 2016-03-09 in JBDS 9.1.0.CR1 (build from 2 days ago).
> I start cdk, the docker connection is created, but it doesn't work:
> {code}
> org.eclipse.linuxtools.docker.core.DockerException: com.spotify.docker.client.DockerException: java.util.concurrent.ExecutionException: javax.ws.rs.ProcessingException: javax.net.ssl.SSLHandshakeException: sun.security.validator.ValidatorException: PKIX path validation failed: java.security.cert.CertPathValidatorException: signature check failed
> at org.eclipse.linuxtools.internal.docker.core.DockerConnection.listImages(DockerConnection.java:787)
> at org.eclipse.linuxtools.internal.docker.core.DockerConnection.getImages(DockerConnection.java:750)
> at org.eclipse.linuxtools.internal.docker.ui.views.DockerExplorerContentProvider$5.run(DockerExplorerContentProvider.java:241)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> Caused by: com.spotify.docker.client.DockerException: java.util.concurrent.ExecutionException: javax.ws.rs.ProcessingException: javax.net.ssl.SSLHandshakeException: sun.security.validator.ValidatorException: PKIX path validation failed: java.security.cert.CertPathValidatorException: signature check failed
> at com.spotify.docker.client.DefaultDockerClient.propagate(DefaultDockerClient.java:1141)
> at com.spotify.docker.client.DefaultDockerClient.request(DefaultDockerClient.java:1072)
> at com.spotify.docker.client.DefaultDockerClient.listImages(DefaultDockerClient.java:354)
> at org.eclipse.linuxtools.internal.docker.core.DockerConnection.listImages(DockerConnection.java:780)
> ... 3 more
> Caused by: java.util.concurrent.ExecutionException: javax.ws.rs.ProcessingException: javax.net.ssl.SSLHandshakeException: sun.security.validator.ValidatorException: PKIX path validation failed: java.security.cert.CertPathValidatorException: signature check failed
> at jersey.repackaged.com.google.common.util.concurrent.AbstractFuture$Sync.getValue(AbstractFuture.java:306)
> at jersey.repackaged.com.google.common.util.concurrent.AbstractFuture$Sync.get(AbstractFuture.java:293)
> at jersey.repackaged.com.google.common.util.concurrent.AbstractFuture.get(AbstractFuture.java:116)
> at com.spotify.docker.client.DefaultDockerClient.request(DefaultDockerClient.java:1070)
> ... 5 more
> Caused by: javax.ws.rs.ProcessingException: javax.net.ssl.SSLHandshakeException: sun.security.validator.ValidatorException: PKIX path validation failed: java.security.cert.CertPathValidatorException: signature check failed
> at org.glassfish.jersey.apache.connector.ApacheConnector.apply(ApacheConnector.java:517)
> at org.glassfish.jersey.apache.connector.ApacheConnector$1.run(ApacheConnector.java:527)
> at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at jersey.repackaged.com.google.common.util.concurrent.MoreExecutors$SameThreadExecutorService.execute(MoreExecutors.java:293)
> at jersey.repackaged.com.google.common.util.concurrent.AbstractListeningExecutorService.submit(AbstractListeningExecutorService.java:49)
> at jersey.repackaged.com.google.common.util.concurrent.AbstractListeningExecutorService.submit(AbstractListeningExecutorService.java:45)
> at org.glassfish.jersey.apache.connector.ApacheConnector.apply(ApacheConnector.java:523)
> at org.glassfish.jersey.client.ClientRuntime$1.run(ClientRuntime.java:169)
> at org.glassfish.jersey.internal.Errors$1.call(Errors.java:271)
> at org.glassfish.jersey.internal.Errors$1.call(Errors.java:267)
> at org.glassfish.jersey.internal.Errors.process(Errors.java:315)
> at org.glassfish.jersey.internal.Errors.process(Errors.java:297)
> at org.glassfish.jersey.internal.Errors.process(Errors.java:267)
> at org.glassfish.jersey.process.internal.RequestScope.runInScope(RequestScope.java:320)
> at org.glassfish.jersey.client.ClientRuntime$2.run(ClientRuntime.java:201)
> at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: javax.net.ssl.SSLHandshakeException: sun.security.validator.ValidatorException: PKIX path validation failed: java.security.cert.CertPathValidatorException: signature check failed
> at sun.security.ssl.Alerts.getSSLException(Alerts.java:192)
> at sun.security.ssl.SSLSocketImpl.fatal(SSLSocketImpl.java:1949)
> at sun.security.ssl.Handshaker.fatalSE(Handshaker.java:302)
> at sun.security.ssl.Handshaker.fatalSE(Handshaker.java:296)
> at sun.security.ssl.ClientHandshaker.serverCertificate(ClientHandshaker.java:1506)
> at sun.security.ssl.ClientHandshaker.processMessage(ClientHandshaker.java:216)
> at sun.security.ssl.Handshaker.processLoop(Handshaker.java:979)
> at sun.security.ssl.Handshaker.process_record(Handshaker.java:914)
> at sun.security.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:1062)
> at sun.security.ssl.SSLSocketImpl.performInitialHandshake(SSLSocketImpl.java:1375)
> at sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1403)
> at sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1387)
> at org.apache.http.conn.ssl.SSLConnectionSocketFactory.createLayeredSocket(SSLConnectionSocketFactory.java:290)
> at org.apache.http.conn.ssl.SSLConnectionSocketFactory.connectSocket(SSLConnectionSocketFactory.java:259)
> at org.apache.http.impl.conn.HttpClientConnectionOperator.connect(HttpClientConnectionOperator.java:125)
> at org.apache.http.impl.conn.PoolingHttpClientConnectionManager.connect(PoolingHttpClientConnectionManager.java:319)
> at org.apache.http.impl.execchain.MainClientExec.establishRoute(MainClientExec.java:363)
> at org.apache.http.impl.execchain.MainClientExec.execute(MainClientExec.java:219)
> at org.apache.http.impl.execchain.ProtocolExec.execute(ProtocolExec.java:195)
> at org.apache.http.impl.execchain.RetryExec.execute(RetryExec.java:86)
> at org.apache.http.impl.execchain.RedirectExec.execute(RedirectExec.java:108)
> at org.apache.http.impl.client.InternalHttpClient.doExecute(InternalHttpClient.java:184)
> at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:72)
> at org.glassfish.jersey.apache.connector.ApacheConnector.apply(ApacheConnector.java:469)
> ... 20 more
> Caused by: sun.security.validator.ValidatorException: PKIX path validation failed: java.security.cert.CertPathValidatorException: signature check failed
> at sun.security.validator.PKIXValidator.doValidate(PKIXValidator.java:352)
> at sun.security.validator.PKIXValidator.engineValidate(PKIXValidator.java:260)
> at sun.security.validator.Validator.validate(Validator.java:260)
> at sun.security.ssl.X509TrustManagerImpl.validate(X509TrustManagerImpl.java:324)
> at sun.security.ssl.X509TrustManagerImpl.checkTrusted(X509TrustManagerImpl.java:229)
> at sun.security.ssl.X509TrustManagerImpl.checkServerTrusted(X509TrustManagerImpl.java:124)
> at sun.security.ssl.ClientHandshaker.serverCertificate(ClientHandshaker.java:1488)
> ... 39 more
> Caused by: java.security.cert.CertPathValidatorException: signature check failed
> at sun.security.provider.certpath.PKIXMasterCertPathValidator.validate(PKIXMasterCertPathValidator.java:135)
> at sun.security.provider.certpath.PKIXCertPathValidator.validate(PKIXCertPathValidator.java:219)
> at sun.security.provider.certpath.PKIXCertPathValidator.validate(PKIXCertPathValidator.java:140)
> at sun.security.provider.certpath.PKIXCertPathValidator.engineValidate(PKIXCertPathValidator.java:79)
> at java.security.cert.CertPathValidator.validate(CertPathValidator.java:292)
> at sun.security.validator.PKIXValidator.doValidate(PKIXValidator.java:347)
> ... 45 more
> Caused by: java.security.SignatureException: Signature does not match.
> at sun.security.x509.X509CertImpl.verify(X509CertImpl.java:424)
> at sun.security.provider.certpath.BasicChecker.verifySignature(BasicChecker.java:166)
> at sun.security.provider.certpath.BasicChecker.check(BasicChecker.java:147)
> at sun.security.provider.certpath.PKIXMasterCertPathValidator.validate(PKIXMasterCertPathValidator.java:125)
> ... 50 more
> {code}
> This looks similar to JBIDE-21733 . But in this case it doesn't work even from terminal:
> {code}
> $ eval "$(vagrant service-manager env docker)"
> $ docker ps
> An error occurred trying to connect: Get https://10.1.2.2:2376/v1.20/containers/json: x509: certificate signed by unknown authority (possibly because of "crypto/rsa: verification error" while trying to verify candidate authority certificate "example.com")
> {code}
> So yeah, this does not seem like the problem is on our site, but let's keep this JIRA for tracking anyway.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-21829) Error when starting an OpenShift Server immediately after workspace startup
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21829?page=com.atlassian.jira.plugi... ]
Fred Bricon commented on JBIDE-21829:
-------------------------------------
Obviously, but the problem here is, the user connects to OpenShift and immediately after, 2 sets of queries are sent to the server. 1 as anonymous, the 2nd as openshift-dev (look at the log in the previous comment)
> Error when starting an OpenShift Server immediately after workspace startup
> ---------------------------------------------------------------------------
>
> Key: JBIDE-21829
> URL: https://issues.jboss.org/browse/JBIDE-21829
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.Beta2
> Reporter: Xavier Coulon
> Assignee: Jeff Cantrill
> Fix For: 4.3.1.CR1
>
>
> I get the following error when my runtime Eclipse starts with the Server Editor opened on an OpenShift Server Adapter:
> {code}
> !ENTRY org.eclipse.core.jobs 4 2 2016-03-08 15:54:58.597
> !MESSAGE An internal error occurred during: "Setting connection, deploy project...".
> !STACK 0
> com.openshift.restclient.authorization.ResourceForbiddenException: User "test-admin" cannot list all services in the cluster
> at com.openshift.internal.restclient.DefaultClient.createOpenShiftException(DefaultClient.java:477)
> at com.openshift.internal.restclient.DefaultClient.list(DefaultClient.java:152)
> at com.openshift.internal.restclient.DefaultClient.list(DefaultClient.java:133)
> at com.openshift.internal.restclient.DefaultClient.list(DefaultClient.java:128)
> at org.jboss.tools.openshift.core.connection.Connection.retryList(Connection.java:434)
> at org.jboss.tools.openshift.core.connection.Connection.getResources(Connection.java:377)
> at org.jboss.tools.openshift.core.server.OpenShiftServerUtils.getService(OpenShiftServerUtils.java:267)
> at org.jboss.tools.openshift.core.server.OpenShiftServerUtils.getService(OpenShiftServerUtils.java:256)
> at org.jboss.tools.openshift.internal.ui.server.OpenShiftServerEditorSection$13.run(OpenShiftServerEditorSection.java:486)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> {code}
> This error also happens when the editor is closed at start-up and opened later on.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-21829) Error when starting an OpenShift Server immediately after workspace startup
by Jeff Cantrill (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21829?page=com.atlassian.jira.plugi... ]
Jeff Cantrill commented on JBIDE-21829:
---------------------------------------
[~fbricon] OpenShift as a general policy does not allow anonymous access to resources; its the default policy. There is no way around this other then relaxing the policy (admins are unlikely to do this) or authenticating, which seems reasonable.
> Error when starting an OpenShift Server immediately after workspace startup
> ---------------------------------------------------------------------------
>
> Key: JBIDE-21829
> URL: https://issues.jboss.org/browse/JBIDE-21829
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.Beta2
> Reporter: Xavier Coulon
> Assignee: Jeff Cantrill
> Fix For: 4.3.1.CR1
>
>
> I get the following error when my runtime Eclipse starts with the Server Editor opened on an OpenShift Server Adapter:
> {code}
> !ENTRY org.eclipse.core.jobs 4 2 2016-03-08 15:54:58.597
> !MESSAGE An internal error occurred during: "Setting connection, deploy project...".
> !STACK 0
> com.openshift.restclient.authorization.ResourceForbiddenException: User "test-admin" cannot list all services in the cluster
> at com.openshift.internal.restclient.DefaultClient.createOpenShiftException(DefaultClient.java:477)
> at com.openshift.internal.restclient.DefaultClient.list(DefaultClient.java:152)
> at com.openshift.internal.restclient.DefaultClient.list(DefaultClient.java:133)
> at com.openshift.internal.restclient.DefaultClient.list(DefaultClient.java:128)
> at org.jboss.tools.openshift.core.connection.Connection.retryList(Connection.java:434)
> at org.jboss.tools.openshift.core.connection.Connection.getResources(Connection.java:377)
> at org.jboss.tools.openshift.core.server.OpenShiftServerUtils.getService(OpenShiftServerUtils.java:267)
> at org.jboss.tools.openshift.core.server.OpenShiftServerUtils.getService(OpenShiftServerUtils.java:256)
> at org.jboss.tools.openshift.internal.ui.server.OpenShiftServerEditorSection$13.run(OpenShiftServerEditorSection.java:486)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> {code}
> This error also happens when the editor is closed at start-up and opened later on.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-21895) Resource name collisions after deleting and recreating the application
by Jeff Cantrill (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21895?page=com.atlassian.jira.plugi... ]
Jeff Cantrill commented on JBIDE-21895:
---------------------------------------
[~fbricon] I have not heard of such a feature but I'm not certain in makes sense in the OpenShift context. The entire system is based on loose coupling where you could add pieces as needed. The CLI provides a way to delete things by label which we could replicate in our delete logic. This assumes, however, that you have labeled everything you hope to delete with the same labels. Additionally, you need to be prepared to accept deleting resources that may also match your label selector. We would probably should allow either multi resource delete by you choosing those resources, or maybe offer you the option to delete by label.
> Resource name collisions after deleting and recreating the application
> ----------------------------------------------------------------------
>
> Key: JBIDE-21895
> URL: https://issues.jboss.org/browse/JBIDE-21895
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.CR1
> Reporter: Pavol Srna
> Fix For: 4.4.x
>
> Attachments: Screen Shot 2016-03-17 at 16.19.05.png
>
>
> 1) Create e.g. node application in a openshift project
> 2) Right click from project explorer -> Delete the application
> 3) repeat step 1)
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-21895) Resource name collisions after deleting and recreating the application
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21895?page=com.atlassian.jira.plugi... ]
Fred Bricon commented on JBIDE-21895:
-------------------------------------
I'm assuming that by deleting the application you mean deleting the service.
Currently, deleting a specific resource in openshift doesn't automatically propagates the deletion of other linked resources.
[~jcantrill] is this something planned for the future?
We could implement something on the eclipse side, where we collect linked resources and perform as many delete request as necessary, but implementing this feature for 4.3.1 is unrealistic
The best workaround is to delete the project. The worst workaround is to select the project, go in the properties view and delete all resources one by one
> Resource name collisions after deleting and recreating the application
> ----------------------------------------------------------------------
>
> Key: JBIDE-21895
> URL: https://issues.jboss.org/browse/JBIDE-21895
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.CR1
> Reporter: Pavol Srna
> Fix For: 4.4.x
>
> Attachments: Screen Shot 2016-03-17 at 16.19.05.png
>
>
> 1) Create e.g. node application in a openshift project
> 2) Right click from project explorer -> Delete the application
> 3) repeat step 1)
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years