[JBoss JIRA] (JBIDE-21051) JPA project building crashes
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21051?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-21051:
-------------------------------
Fix Version/s: 4.4.2.AM3
(was: 4.4.2.AM1)
> JPA project building crashes
> ----------------------------
>
> Key: JBIDE-21051
> URL: https://issues.jboss.org/browse/JBIDE-21051
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: hibernate
> Affects Versions: 4.3.0.Final
> Environment: Mars SR1 (running on java8), Windows 7
> Reporter: Jesper Skov
> Assignee: Koen Aers
> Priority: Minor
> Fix For: 4.4.2.AM3
>
> Attachments: hibernate.ejb.zip
>
>
> We have been using the 'generic' platform for JPA projects for a long time.
> With Mars.Sr1 and latest jbosstools release, I figured I should give the Hibernate platform a chance again.
> Unfortunately, it fails with the below stacktrace.
> It is a in a EAP5 project (yes, I know. we have started migration to EAP6) with JPA 1.0 facet.
> The project has many JPA annotated files, so I can't easily figure out which one may contain the trigger.
> Can I enable logging in the hibernate plugin somehow to help pin point the file and its annotations?
> {code}
> !ENTRY org.eclipse.jpt.jpa.core 4 0 2015-11-04 14:36:10.235
> !MESSAGE
> !STACK 0
> java.lang.NullPointerException
> at org.eclipse.jpt.jpa.core.internal.context.java.AbstractJavaPersistentAttribute.updateMapping(AbstractJavaPersistentAttribute.java:408)
> at org.eclipse.jpt.jpa.core.internal.context.java.AbstractJavaPersistentAttribute.update(AbstractJavaPersistentAttribute.java:109)
> at org.eclipse.jpt.jpa.core.internal.context.java.AbstractJavaPersistentType.syncFieldAttributes(AbstractJavaPersistentType.java:581)
> at org.eclipse.jpt.jpa.core.internal.context.java.AbstractJavaPersistentType.syncFieldAccessAttributes(AbstractJavaPersistentType.java:508)
> at org.eclipse.jpt.jpa.core.internal.context.java.AbstractJavaPersistentType.updateAttributes(AbstractJavaPersistentType.java:493)
> at org.eclipse.jpt.jpa.core.internal.context.java.AbstractJavaPersistentType.update(AbstractJavaPersistentType.java:101)
> at org.eclipse.jpt.jpa.core.internal.jpa1.context.persistence.GenericClassRef.updateJavaManagedType(GenericClassRef.java:192)
> at org.eclipse.jpt.jpa.core.internal.jpa1.context.persistence.GenericClassRef.update(GenericClassRef.java:123)
> at org.jboss.tools.hibernate.jpt.core.internal.context.persistence.HibernateClassRef.update(HibernateClassRef.java:88)
> at org.eclipse.jpt.jpa.core.internal.context.AbstractJpaContextModel.updateModels(AbstractJpaContextModel.java:73)
> at org.eclipse.jpt.jpa.core.internal.context.persistence.AbstractPersistenceUnit.update(AbstractPersistenceUnit.java:290)
> at org.jboss.tools.hibernate.jpt.core.internal.context.HibernatePersistenceUnit.update(HibernatePersistenceUnit.java:94)
> at org.eclipse.jpt.jpa.core.internal.context.AbstractJpaContextModel.updateModels(AbstractJpaContextModel.java:73)
> at org.eclipse.jpt.jpa.core.internal.jpa1.context.persistence.GenericPersistence.update(GenericPersistence.java:75)
> at org.eclipse.jpt.jpa.core.internal.jpa1.context.persistence.GenericPersistenceXml.syncPersistence(GenericPersistenceXml.java:140)
> at org.eclipse.jpt.jpa.core.internal.jpa1.context.persistence.GenericPersistenceXml.updatePersistence(GenericPersistenceXml.java:97)
> at org.eclipse.jpt.jpa.core.internal.jpa1.context.persistence.GenericPersistenceXml.update(GenericPersistenceXml.java:93)
> at org.eclipse.jpt.jpa.core.internal.jpa1.context.GenericContextRoot.syncPersistenceXml(GenericContextRoot.java:128)
> at org.eclipse.jpt.jpa.core.internal.jpa1.context.GenericContextRoot.updatePersistenceXml(GenericContextRoot.java:162)
> at org.eclipse.jpt.jpa.core.internal.jpa1.context.GenericContextRoot.update(GenericContextRoot.java:78)
> at org.eclipse.jpt.jpa.core.internal.AbstractJpaProject.update(AbstractJpaProject.java:1994)
> at org.eclipse.jpt.jpa.core.internal.AbstractJpaProject$UpdateJobCommand.execute(AbstractJpaProject.java:1981)
> at org.eclipse.jpt.common.core.internal.utility.command.RepeatingJobCommandWrapper.executeCommand(RepeatingJobCommandWrapper.java:207)
> at org.eclipse.jpt.common.core.internal.utility.command.NotifyingRepeatingJobCommandWrapper.executeCommand(NotifyingRepeatingJobCommandWrapper.java:68)
> at org.eclipse.jpt.common.core.internal.utility.command.RepeatingJobCommandWrapper.execute_(RepeatingJobCommandWrapper.java:192)
> at org.eclipse.jpt.common.core.internal.utility.command.RepeatingJobCommandWrapper$StartJobCommand.execute(RepeatingJobCommandWrapper.java:172)
> at org.eclipse.jpt.common.core.internal.utility.command.DefaultJobCommandContext.execute(DefaultJobCommandContext.java:38)
> at org.eclipse.jpt.common.core.internal.utility.command.RepeatingJobCommandWrapper.executeStartCommand(RepeatingJobCommandWrapper.java:157)
> at org.eclipse.jpt.common.core.internal.utility.command.RepeatingJobCommandWrapper.execute(RepeatingJobCommandWrapper.java:147)
> at org.eclipse.jpt.jpa.core.internal.AbstractJpaProject.update(AbstractJpaProject.java:1973)
> at org.eclipse.jpt.jpa.core.internal.AbstractJpaProject.initializeContextModel(AbstractJpaProject.java:303)
> at org.eclipse.jpt.jpa.core.internal.AbstractJpaProject.<init>(AbstractJpaProject.java:264)
> at org.jboss.tools.hibernate.jpt.core.internal.HibernateJpaProject.<init>(HibernateJpaProject.java:71)
> at org.jboss.tools.hibernate.jpt.core.internal.HibernateAbstractJpaFactory.buildJpaProject(HibernateAbstractJpaFactory.java:107)
> at org.jboss.tools.hibernate.jpt.core.internal.jpa2.HibernateJpaFactory2_0.buildJpaProject(HibernateJpaFactory2_0.java:89)
> at org.eclipse.jpt.jpa.core.internal.InternalJpaProjectManager.buildJpaProject(InternalJpaProjectManager.java:647)
> at org.eclipse.jpt.jpa.core.internal.InternalJpaProjectManager.buildJpaProject(InternalJpaProjectManager.java:635)
> at org.eclipse.jpt.jpa.core.internal.InternalJpaProjectManager.buildJpaProject(InternalJpaProjectManager.java:628)
> at org.eclipse.jpt.jpa.core.internal.InternalJpaProjectManager.addJpaProject(InternalJpaProjectManager.java:609)
> at org.eclipse.jpt.jpa.core.internal.InternalJpaProjectManager.buildJpaProject_(InternalJpaProjectManager.java:312)
> at org.eclipse.jpt.jpa.core.internal.InternalJpaProjectManager$BuildJpaProjectCommand.execute(InternalJpaProjectManager.java:306)
> at org.eclipse.jpt.common.core.internal.utility.command.CommandJobCommandAdapter.execute(CommandJobCommandAdapter.java:50)
> at org.eclipse.jpt.common.core.internal.utility.command.JobCommandJob.run(JobCommandJob.java:42)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> !ENTRY org.eclipse.jpt.jpa.core 4 0 2015-11-04 14:36:33.814
> !MESSAGE
> !STACK 0
> java.lang.UnsupportedOperationException
> at org.jboss.tools.hibernate.jpt.core.internal.resource.java.GenericGeneratorAnnotationDefinition.buildAnnotation(GenericGeneratorAnnotationDefinition.java:51)
> at org.eclipse.jpt.jpa.core.internal.JpaAnnotationProvider.buildAnnotation(JpaAnnotationProvider.java:78)
> at org.eclipse.jpt.common.core.internal.resource.java.binary.BinaryAnnotatedElement.buildAnnotation(BinaryAnnotatedElement.java:236)
> at org.eclipse.jpt.common.core.internal.resource.java.binary.BinaryAnnotatedElement$AnnotationContainer.addAnnotation(BinaryAnnotatedElement.java:360)
> at org.eclipse.jpt.common.core.internal.resource.java.binary.BinaryAnnotatedElement$AnnotationContainer.initializeFromStandaloneAnnotation(BinaryAnnotatedElement.java:356)
> at org.eclipse.jpt.common.core.internal.resource.java.binary.BinaryAnnotatedElement.addAnnotation(BinaryAnnotatedElement.java:106)
> at org.eclipse.jpt.common.core.internal.resource.java.binary.BinaryAnnotatedElement.initializeAnnotations(BinaryAnnotatedElement.java:71)
> at org.eclipse.jpt.common.core.internal.resource.java.binary.BinaryAnnotatedElement.<init>(BinaryAnnotatedElement.java:65)
> at org.eclipse.jpt.common.core.internal.resource.java.binary.BinaryMember.<init>(BinaryMember.java:44)
> at org.eclipse.jpt.common.core.internal.resource.java.binary.BinaryAttribute.<init>(BinaryAttribute.java:35)
> at org.eclipse.jpt.common.core.internal.resource.java.binary.BinaryField.<init>(BinaryField.java:35)
> at org.eclipse.jpt.common.core.internal.resource.java.binary.BinaryField.<init>(BinaryField.java:31)
> at org.eclipse.jpt.common.core.internal.resource.java.binary.BinaryType.buildField(BinaryType.java:281)
> at org.eclipse.jpt.common.core.internal.resource.java.binary.BinaryType$FieldTransformer.transform(BinaryType.java:264)
> at org.eclipse.jpt.common.core.internal.resource.java.binary.BinaryType$FieldTransformer.transform(BinaryType.java:1)
> at org.eclipse.jpt.common.utility.internal.iterator.TransformationIterator.next(TransformationIterator.java:54)
> at org.eclipse.jpt.common.utility.internal.collection.CollectionTools.addAll_(CollectionTools.java:72)
> at org.eclipse.jpt.common.utility.internal.collection.CollectionTools.addAll(CollectionTools.java:63)
> at org.eclipse.jpt.common.utility.internal.collection.CollectionTools.addAll(CollectionTools.java:44)
> at org.eclipse.jpt.common.core.internal.resource.java.binary.BinaryType.<init>(BinaryType.java:79)
> at org.eclipse.jpt.common.core.internal.resource.java.binary.BinaryType.<init>(BinaryType.java:70)
> at org.eclipse.jpt.common.core.internal.resource.java.binary.BinaryTypeCache.buildType(BinaryTypeCache.java:87)
> at org.eclipse.jpt.common.core.internal.resource.java.binary.BinaryTypeCache.buildEntry(BinaryTypeCache.java:80)
> at org.eclipse.jpt.common.core.internal.resource.java.binary.BinaryTypeCache.addType(BinaryTypeCache.java:73)
> at org.eclipse.jpt.jpa.core.internal.AbstractJpaProject.buildBinaryExternalJavaResourceType(AbstractJpaProject.java:686)
> at org.eclipse.jpt.jpa.core.internal.AbstractJpaProject.buildExternalJavaResourceType(AbstractJpaProject.java:681)
> at org.eclipse.jpt.jpa.core.internal.AbstractJpaProject.buildExternalJavaResourceType(AbstractJpaProject.java:660)
> at org.eclipse.jpt.jpa.core.internal.AbstractJpaProject.getJavaResourceType(AbstractJpaProject.java:904)
> at org.eclipse.jpt.jpa.core.internal.jpa1.context.persistence.GenericClassRef.resolveJavaResourceType(GenericClassRef.java:207)
> at org.eclipse.jpt.jpa.core.internal.jpa1.context.persistence.GenericClassRef.<init>(GenericClassRef.java:83)
> at org.jboss.tools.hibernate.jpt.core.internal.context.persistence.HibernateClassRef.<init>(HibernateClassRef.java:52)
> at org.jboss.tools.hibernate.jpt.core.internal.context.persistence.HibernatePersistenceXmlContextNodeFactory.buildClassRef(HibernatePersistenceXmlContextNodeFactory.java:46)
> at org.eclipse.jpt.jpa.core.internal.context.persistence.AbstractPersistenceUnit.buildClassRef(AbstractPersistenceUnit.java:869)
> at org.eclipse.jpt.jpa.core.internal.context.persistence.AbstractPersistenceUnit$SpecifiedClassRefContainerAdapter.buildContextElement(AbstractPersistenceUnit.java:914)
> at org.eclipse.jpt.jpa.core.internal.context.persistence.AbstractPersistenceUnit$SpecifiedClassRefContainerAdapter.buildContextElement(AbstractPersistenceUnit.java:1)
> at org.eclipse.jpt.jpa.core.internal.context.AbstractJpaContextModel$Container.initialize(AbstractJpaContextModel.java:319)
> at org.eclipse.jpt.jpa.core.internal.context.AbstractJpaContextModel$SpecifiedContextListContainer.<init>(AbstractJpaContextModel.java:732)
> at org.eclipse.jpt.jpa.core.internal.context.AbstractJpaContextModel.buildSpecifiedContextListContainer(AbstractJpaContextModel.java:737)
> at org.eclipse.jpt.jpa.core.internal.context.persistence.AbstractPersistenceUnit.buildSpecifiedClassRefContainer(AbstractPersistenceUnit.java:904)
> at org.eclipse.jpt.jpa.core.internal.context.persistence.AbstractPersistenceUnit.<init>(AbstractPersistenceUnit.java:238)
> at org.jboss.tools.hibernate.jpt.core.internal.context.HibernatePersistenceUnit.<init>(HibernatePersistenceUnit.java:77)
> at org.jboss.tools.hibernate.jpt.core.internal.context.persistence.HibernatePersistenceXmlContextNodeFactory.buildPersistenceUnit(HibernatePersistenceXmlContextNodeFactory.java:32)
> at org.eclipse.jpt.jpa.core.internal.jpa1.context.persistence.GenericPersistence.buildPersistenceUnit(GenericPersistence.java:195)
> at org.eclipse.jpt.jpa.core.internal.jpa1.context.persistence.GenericPersistence.initializePersistenceUnits(GenericPersistence.java:153)
> at org.eclipse.jpt.jpa.core.internal.jpa1.context.persistence.GenericPersistence.<init>(GenericPersistence.java:59)
> at org.jboss.tools.hibernate.jpt.core.internal.context.persistence.HibernatePersistence.<init>(HibernatePersistence.java:29)
> at org.jboss.tools.hibernate.jpt.core.internal.context.persistence.HibernatePersistenceXmlContextNodeFactory.buildPersistence(HibernatePersistenceXmlContextNodeFactory.java:40)
> at org.eclipse.jpt.jpa.core.internal.jpa1.context.persistence.GenericPersistenceXml.buildRoot(GenericPersistenceXml.java:160)
> at org.eclipse.jpt.jpa.core.internal.jpa1.context.persistence.GenericPersistenceXml.<init>(GenericPersistenceXml.java:68)
> at org.eclipse.jpt.jpa.core.internal.AbstractJpaFactory.buildPersistenceXml(AbstractJpaFactory.java:198)
> at org.eclipse.jpt.jpa.core.internal.jpa1.context.GenericContextRoot.buildPersistenceXml(GenericContextRoot.java:158)
> at org.eclipse.jpt.jpa.core.internal.jpa1.context.GenericContextRoot.buildPersistenceXml(GenericContextRoot.java:96)
> at org.eclipse.jpt.jpa.core.internal.jpa1.context.GenericContextRoot.<init>(GenericContextRoot.java:63)
> at org.eclipse.jpt.jpa.core.internal.AbstractJpaFactory.buildContextRoot(AbstractJpaFactory.java:191)
> at org.eclipse.jpt.jpa.core.internal.AbstractJpaProject.buildContextRoot(AbstractJpaProject.java:290)
> at org.eclipse.jpt.jpa.core.internal.AbstractJpaProject.<init>(AbstractJpaProject.java:261)
> at org.jboss.tools.hibernate.jpt.core.internal.HibernateJpaProject.<init>(HibernateJpaProject.java:71)
> at org.jboss.tools.hibernate.jpt.core.internal.HibernateAbstractJpaFactory.buildJpaProject(HibernateAbstractJpaFactory.java:107)
> at org.eclipse.jpt.jpa.core.internal.InternalJpaProjectManager.buildJpaProject(InternalJpaProjectManager.java:647)
> at org.eclipse.jpt.jpa.core.internal.InternalJpaProjectManager.buildJpaProject(InternalJpaProjectManager.java:635)
> at org.eclipse.jpt.jpa.core.internal.InternalJpaProjectManager.buildJpaProject(InternalJpaProjectManager.java:628)
> at org.eclipse.jpt.jpa.core.internal.InternalJpaProjectManager.addJpaProject(InternalJpaProjectManager.java:609)
> at org.eclipse.jpt.jpa.core.internal.InternalJpaProjectManager.rebuildJpaProject_(InternalJpaProjectManager.java:541)
> at org.eclipse.jpt.jpa.core.internal.InternalJpaProjectManager$RebuildJpaProjectCommand.execute(InternalJpaProjectManager.java:529)
> at org.eclipse.jpt.jpa.core.internal.InternalJpaProjectManager.waitToExecute(InternalJpaProjectManager.java:1097)
> at org.eclipse.jpt.jpa.core.internal.InternalJpaProjectManager.waitToExecute(InternalJpaProjectManager.java:1076)
> at org.eclipse.jpt.jpa.core.internal.InternalJpaProjectManager.rebuildJpaProject(InternalJpaProjectManager.java:512)
> at org.eclipse.jpt.jpa.core.internal.ProjectAdapterFactory$JpaProjectReference.rebuild(ProjectAdapterFactory.java:117)
> at org.eclipse.jpt.jpa.ui.internal.properties.JpaProjectPropertiesPage.rebuildProject_(JpaProjectPropertiesPage.java:869)
> at org.eclipse.jpt.jpa.ui.internal.properties.JpaProjectPropertiesPage.rebuildProject(JpaProjectPropertiesPage.java:860)
> at org.eclipse.jpt.common.ui.internal.properties.JptProjectPropertiesPage.performOk_(JptProjectPropertiesPage.java:339)
> at org.eclipse.jpt.common.ui.internal.properties.JptProjectPropertiesPage$OkRunnableWithProgress$OkWorkspaceRunnable.run(JptProjectPropertiesPage.java:322)
> at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2241)
> at org.eclipse.jpt.common.ui.internal.properties.JptProjectPropertiesPage$OkRunnableWithProgress.run(JptProjectPropertiesPage.java:302)
> at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:119)
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 6 months
[JBoss JIRA] (JBIDE-20108) Cannot connect to remote server in JMX Navigator - Authentication fails
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20108?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-20108:
-------------------------------
Fix Version/s: 4.4.2.AM2
(was: 4.4.2.AM1)
> Cannot connect to remote server in JMX Navigator - Authentication fails
> -----------------------------------------------------------------------
>
> Key: JBIDE-20108
> URL: https://issues.jboss.org/browse/JBIDE-20108
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: jmx
> Affects Versions: 4.3.0.Beta1
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Fix For: 4.4.2.AM2
>
>
> When I try to connect to a remote server via JMX Navigator, it fails on authentication:
> {code}
> !ENTRY org.jboss.ide.eclipse.as.jmx.integration 4 0 2015-06-17 18:07:30.854
> !MESSAGE Error connecting to jmx for server JBoss EAP 6.4 marvin
> !STACK 1
> org.jboss.tools.jmx.core.JMXException: Authentication against the remote JBoss instance has failed. Please verify your management credentials in the server editor.
> at org.jboss.ide.eclipse.as.jmx.integration.JBoss71ServerConnection.createConnection(JBoss71ServerConnection.java:94)
> at org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnection.run(JBossServerConnection.java:202)
> at org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnection.run(JBossServerConnection.java:162)
> at org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnection.connectToStartedServer(JBossServerConnection.java:332)
> at org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnection.connect(JBossServerConnection.java:76)
> at org.jboss.tools.jmx.core.ConnectJob.run(ConnectJob.java:29)
> at org.jboss.tools.jmx.ui.internal.actions.DoubleClickAction$1.run(DoubleClickAction.java:71)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> Caused by: javax.security.sasl.SaslException: Authentication failed: the server presented no authentication mechanisms
> at org.jboss.remoting3.remote.ClientConnectionOpenListener$Capabilities.handleEvent(ClientConnectionOpenListener.java:388)
> at org.jboss.remoting3.remote.ClientConnectionOpenListener$Capabilities.handleEvent(ClientConnectionOpenListener.java:242)
> at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:72)
> at org.xnio.channels.TranslatingSuspendableChannel.handleReadable(TranslatingSuspendableChannel.java:189)
> at org.xnio.channels.TranslatingSuspendableChannel$1.handleEvent(TranslatingSuspendableChannel.java:103)
> at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:72)
> at org.xnio.channels.TranslatingSuspendableChannel.handleReadable(TranslatingSuspendableChannel.java:189)
> at org.xnio.ssl.JsseConnectedSslStreamChannel.handleReadable(JsseConnectedSslStreamChannel.java:183)
> at org.xnio.channels.TranslatingSuspendableChannel$1.handleEvent(TranslatingSuspendableChannel.java:103)
> at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:72)
> at org.xnio.nio.NioHandle.run(NioHandle.java:90)
> at org.xnio.nio.WorkerThread.run(WorkerThread.java:198)
> at ...asynchronous invocation...(Unknown Source)
> at org.jboss.remoting3.EndpointImpl.doConnect(EndpointImpl.java:270)
> at org.jboss.remoting3.EndpointImpl.doConnect(EndpointImpl.java:251)
> at org.jboss.remoting3.EndpointImpl.connect(EndpointImpl.java:349)
> at org.jboss.remoting3.EndpointImpl.connect(EndpointImpl.java:333)
> at org.jboss.remotingjmx.RemotingConnector.internalRemotingConnect(RemotingConnector.java:230)
> at org.jboss.remotingjmx.RemotingConnector.internalConnect(RemotingConnector.java:151)
> at org.jboss.remotingjmx.RemotingConnector.connect(RemotingConnector.java:102)
> at javax.management.remote.JMXConnectorFactory.connect(JMXConnectorFactory.java:270)
> at org.jboss.ide.eclipse.as.jmx.integration.JBoss71ServerConnection.createConnection(JBoss71ServerConnection.java:84)
> ... 7 more
> !SUBENTRY 1 org.jboss.ide.eclipse.as.core 4 0 2015-06-17 18:07:30.854
> !MESSAGE Authentication against the remote JBoss instance has failed. Please verify your management credentials in the server editor.
> !STACK 0
> javax.security.sasl.SaslException: Authentication failed: the server presented no authentication mechanisms
> at org.jboss.remoting3.remote.ClientConnectionOpenListener$Capabilities.handleEvent(ClientConnectionOpenListener.java:388)
> at org.jboss.remoting3.remote.ClientConnectionOpenListener$Capabilities.handleEvent(ClientConnectionOpenListener.java:242)
> at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:72)
> at org.xnio.channels.TranslatingSuspendableChannel.handleReadable(TranslatingSuspendableChannel.java:189)
> at org.xnio.channels.TranslatingSuspendableChannel$1.handleEvent(TranslatingSuspendableChannel.java:103)
> at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:72)
> at org.xnio.channels.TranslatingSuspendableChannel.handleReadable(TranslatingSuspendableChannel.java:189)
> at org.xnio.ssl.JsseConnectedSslStreamChannel.handleReadable(JsseConnectedSslStreamChannel.java:183)
> at org.xnio.channels.TranslatingSuspendableChannel$1.handleEvent(TranslatingSuspendableChannel.java:103)
> at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:72)
> at org.xnio.nio.NioHandle.run(NioHandle.java:90)
> at org.xnio.nio.WorkerThread.run(WorkerThread.java:198)
> at ...asynchronous invocation...(Unknown Source)
> at org.jboss.remoting3.EndpointImpl.doConnect(EndpointImpl.java:270)
> at org.jboss.remoting3.EndpointImpl.doConnect(EndpointImpl.java:251)
> at org.jboss.remoting3.EndpointImpl.connect(EndpointImpl.java:349)
> at org.jboss.remoting3.EndpointImpl.connect(EndpointImpl.java:333)
> at org.jboss.remotingjmx.RemotingConnector.internalRemotingConnect(RemotingConnector.java:230)
> at org.jboss.remotingjmx.RemotingConnector.internalConnect(RemotingConnector.java:151)
> at org.jboss.remotingjmx.RemotingConnector.connect(RemotingConnector.java:102)
> at javax.management.remote.JMXConnectorFactory.connect(JMXConnectorFactory.java:270)
> at org.jboss.ide.eclipse.as.jmx.integration.JBoss71ServerConnection.createConnection(JBoss71ServerConnection.java:84)
> at org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnection.run(JBossServerConnection.java:202)
> at org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnection.run(JBossServerConnection.java:162)
> at org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnection.connectToStartedServer(JBossServerConnection.java:332)
> at org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnection.connect(JBossServerConnection.java:76)
> at org.jboss.tools.jmx.core.ConnectJob.run(ConnectJob.java:29)
> at org.jboss.tools.jmx.ui.internal.actions.DoubleClickAction$1.run(DoubleClickAction.java:71)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> {code}
> This is different than JBIDE-19463 where the main problem was the missing runtime and we assumed that otherwise it would work.
> Note: I tried WildFly 8.2, WildFly 9.0.0.CR2, EAP 6.4 and all failed the same way.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 6 months
[JBoss JIRA] (JBDS-4014) Track rh-eclipse46-devstudio-*.rpm version usage
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-4014?page=com.atlassian.jira.plugin.... ]
Nick Boldt reassigned JBDS-4014:
--------------------------------
Assignee: Alexander Kurtakov (was: Alexey Kazakov)
> Track rh-eclipse46-devstudio-*.rpm version usage
> ------------------------------------------------
>
> Key: JBDS-4014
> URL: https://issues.jboss.org/browse/JBDS-4014
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Feature Request
> Components: usage
> Reporter: Alexey Kazakov
> Assignee: Alexander Kurtakov
> Priority: Critical
> Fix For: 10.2.0.AM1
>
>
> We need to distinguish the following use cases:
> 1) Devstudio installed via RPM
> 2) Devstudio installed via P2 but on top of the "base" eclipse rpm
> 3) Devstudio installed traditionally (jar installer or p2)
> As a bonus we could want to track if the DTS + devstudio rpms were both installed.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 6 months
[JBoss JIRA] (JBIDE-22382) Use different icons for EAP server and Red Hat Central
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22382?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-22382:
-------------------------------
Fix Version/s: 4.4.2.AM3
(was: 4.4.2.AM1)
> Use different icons for EAP server and Red Hat Central
> ------------------------------------------------------
>
> Key: JBIDE-22382
> URL: https://issues.jboss.org/browse/JBIDE-22382
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: central, server
> Affects Versions: 4.4.0.Alpha2
> Reporter: Marián Labuda
> Assignee: James Cobb
> Priority: Minor
> Labels: respin-a
> Fix For: 4.4.2.AM3
>
> Attachments: central-rhd-icon.png, fullIDE.png, tools_rebrand.png
>
>
> If there is an EAP server present in Servers view, workbench tool bar contains 2 same icons - Select a default server icon is same as Red Hat Central icon. We should make this explicitly different.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 6 months
[JBoss JIRA] (JBIDE-22713) IOException in CentralHelper.extractIfNeeded
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22713?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-22713:
-------------------------------
Fix Version/s: 4.4.2.AM2
(was: 4.4.2.AM1)
> IOException in CentralHelper.extractIfNeeded
> --------------------------------------------
>
> Key: JBIDE-22713
> URL: https://issues.jboss.org/browse/JBIDE-22713
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central
> Affects Versions: 4.3.0.Final
> Reporter: Automated Error Reporting Bot
> Assignee: Jeff MAURY
> Fix For: 4.4.2.AM2
>
>
> The following problem was reported via the automated error reporting:
> Message: Unable to open C:\eclipse\plugins\org.jboss.tools.central_2.0.1.Final-v20160401-1059-B103\resources\jbosstools-central-webpage.zip
> {noformat}
> java.io.IOException: D:\OneDrive\TreinaWeb\Java Básico\JSE\.metadata\.plugins\org.jboss.tools.central\central\bc8a80b\index.html can not be found
> at org.jboss.tools.central.internal.CentralHelper.extractIfNeeded(CentralHelper.java:203)
> at org.jboss.tools.central.internal.CentralHelper.getCentralPageUrl(CentralHelper.java:122)
> at org.jboss.tools.central.internal.CentralHelper.getCentralUrl(CentralHelper.java:60)
> at org.jboss.tools.central.editors.GettingStartedHtmlPage$5.run(GettingStartedHtmlPage.java:252)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> {noformat}
> Bundles:
> | org.eclipse.core.jobs | 3.7.0.v20150330-2103 | 3.8.0.v20160509-0411 |
> | org.jboss.tools.central | 2.0.1.Final-v20160401-1059-B103 | 2.1.0.qualifier |
> Operating Systems:
> | Linux | 3.2.0 | 4.5.7.fc23 |
> | MacOSX | 10.10.5 | 10.11.5 |
> | Windows | 5.1.0 | 10.0.0 |
> The above information is a snapshot of the collected data. Visit [this page|https://redhat.ctrlflow.com/reviewers/#!/problems/571659e0e4b055563f...] for the latest data.
> Thank you for your assistance.
> Your friendly error-reports-inbox.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 6 months
[JBoss JIRA] (JBIDE-22578) Publishing sometimes recursively deletes parent to deploy directory
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22578?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-22578:
-------------------------------
Fix Version/s: 4.4.2.AM2
(was: 4.4.2.AM1)
> Publishing sometimes recursively deletes parent to deploy directory
> -------------------------------------------------------------------
>
> Key: JBIDE-22578
> URL: https://issues.jboss.org/browse/JBIDE-22578
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.3.1.Final
> Environment: Eclipse Mars.2 Release (4.5.2)
> Java 1.8.0_91
> Windows 7 64-bit
> JBoss EAP 6.4.0
> Reporter: Daniel Atallah
> Assignee: Rob Stryker
> Fix For: 4.4.2.AM2
>
> Attachments: jboss_deployment.jpg, jboss_tools.20160630.stdout.log, servers.xml
>
>
> For a number of weeks we've had a number of occurrences where a eclipse workspace will get corrupted due to the deletion of all files in it.
> It seems to have started happening at the time we updated to the 4.3.1 JBoss Tools from the 4.3.0 JBoss Tools.
> We've been able to track the process doing the deleting to the Eclipse process by using Sysinternals Process Monitor tool (https://technet.microsoft.com/en-us/sysinternals/processmonitor.aspx).
> Our workspaces are structured as follows:
> {noformat}
> WORKSPACEROOT=$DEVROOT\workspacename
> # Custom deploy folder (as specified in the "Deployment" settings for the configured "Red Hat JBoss Enterprise Application Platform 6.1+") Server
> $WORKSPACEROOT\deploy
> # Version Control (Mercurial) working directory containing various Eclipse projects that get published to the Server by the tooling
> $WORKSPACEROOT\src
> # value specified as a "jboss.server.data.dir" property in the Server launch configuration VM arguments
> $WORKSPACEROOT/server/data
> # value specified as a "jboss.server.temp.dir" property in the Server launch configuration VM arguments
> $WORKSPACEROOT/server/tmp
> {noformat}
> The Server is configured to "Automatically publish when resources change".
> What we're seeing is that occasionally when the Server is running and the Mercurial working copy receives updates, the Incremental Publishing that results from these updates somehow tries to recursively delete $WORKSPACEROOT.
> The eclipse log includes the following:
> {noformat}
> !ENTRY org.eclipse.core.resources 4 1 2016-06-07 16:05:57.795
> !MESSAGE Problems occurred refreshing resources
> !SUBENTRY 1 org.eclipse.core.resources 4 1 2016-06-07 16:05:57.795
> !MESSAGE Problem finding next change, code: 5
> !ENTRY org.jboss.ide.eclipse.as.core 4 1644298244 2016-06-07 16:06:09.207
> !MESSAGE Incremental publish failed for module $MODULENAME
> !SUBENTRY 1 org.jboss.ide.eclipse.as.wtp.core 4 1644298251 2016-06-07 16:06:09.207
> !MESSAGE Could not delete $WORKSPACEROOT. May be locked by another process.
> {noformat}
> Any idea what might be happening?
> Is there some debug logging we can enable to get better visibility to what's going on?
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 6 months
[JBoss JIRA] (JBIDE-22878) EAR deployed from DevStudio to EAP contains errorneously named ejbs
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22878?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-22878:
-------------------------------
Fix Version/s: 4.4.2.AM2
(was: 4.4.2.AM1)
> EAR deployed from DevStudio to EAP contains errorneously named ejbs
> -------------------------------------------------------------------
>
> Key: JBIDE-22878
> URL: https://issues.jboss.org/browse/JBIDE-22878
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.2.3.Final, 4.4.0.Final
> Environment: I've observed this problem on a Win7 64 bit machine with Oracle JRE 1.8.0_102 64 bit. It was present in both JBoss Developer Studio 8.1.0.GA and 10.0.0.GA when used in conjunction with embedded Maven installation and JBoss EAP 6.4 target runtime.
> Reporter: Mikhail Kalkov
> Assignee: Rob Stryker
> Fix For: 4.4.2.AM2
>
> Attachments: JBIDE-22878-deployment-assembly.png, screendump.png, test-ear.ear, test-projects.zip
>
>
> I've created a maven-based EAR project that contains serveral ejb modules some of which come from workspace whereas others are downloaded from binary artifact repository. All modules have bundleFileName specified as module-name.jar in order to override the default module-name-version.jar.
> When I right-click on an EAR project and choose Export..., a correct EAR file is built, which looks exactly the same as when I build it from command line. However, when I add this project to an EAP 6.4 server, and check "Deploy projects as compressed archives" option, an EAR with erroneously named ejbs is deployed. the bundleFileName option is namely ignored for EJBs that come from binary artifact repository. See attached screenshot.
> This problem makes it extremely difficult to debug issues that arise only with zipped ear deployments. The only workaround is to comment out bundleFileName lines in test-ear pom.xml as well as possibly fix filenames in persistence.xml, and remember to revert these changes before committing!
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 6 months