[JBoss JIRA] (TEIIDDES-3051) "Intialisation [sic] produced an exception" when starting Server
by Steve Tran (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-3051?page=com.atlassian.jira.plu... ]
Steve Tran updated TEIIDDES-3051:
---------------------------------
Description:
Starting the server always throws this exception. It's non-fatal, but it's been around since JBDS 8.
Here's a snip from the logs.
{code}
!SESSION 2017-03-01 12:36:18.825 -----------------------------------------------
eclipse.buildId=10.3.0.GA-v20170218-1636-B94
java.version=1.8.0_121
java.vendor=Oracle Corporation
BootLoader constants: OS=win32, ARCH=x86_64, WS=win32, NL=en_US
Framework arguments: -product com.jboss.devstudio.core.product
Command-line arguments: -data file:/C:/Users/C031711/workspace/ -os win32 -ws win32 -arch x86_64 -product com.jboss.devstudio.core.product
!ENTRY org.eclipse.egit.ui 2 0 2017-03-01 12:36:26.952
!MESSAGE Warning: The environment variable HOME is not set. The following directory will be used to store the Git
user global configuration and to define the default location to store repositories: 'C:\Users\C031711'. If this is
not correct please set the HOME environment variable and restart Eclipse. Otherwise Git for Windows and
EGit might behave differently since they see different configuration options.
This warning can be switched off on the Team > Git > Confirmations and Warnings preference page.
!ENTRY org.eclipse.epp.logging.aeri.ide 2 17 2017-03-01 12:36:27.847
!MESSAGE Server ‘org.jboss.tools’ failed with exception: Proxy Unacknowledged. ; version: 2.0.3.v20161205-0933
!STACK 0
org.apache.http.client.HttpResponseException: Proxy Unacknowledged
at org.eclipse.epp.internal.logging.aeri.ide.server.mars.HttpResponses$ProgressMonitorResponseHandler.handleResponse(HttpResponses.java:71)
at org.eclipse.epp.internal.logging.aeri.ide.server.mars.HttpResponses$ProgressMonitorResponseStringHandler.handleResponse(HttpResponses.java:93)
at org.eclipse.epp.internal.logging.aeri.ide.server.mars.HttpResponses$ProgressMonitorResponseStringHandler.handleResponse(HttpResponses.java:1)
at org.apache.http.client.fluent.Response.handleResponse(Response.java:90)
at org.eclipse.epp.internal.logging.aeri.ide.server.mars.HttpResponses.getContentWithProgress(HttpResponses.java:56)
at org.eclipse.epp.internal.logging.aeri.ide.server.mars.IO.refreshConfiguration(IO.java:69)
at org.eclipse.epp.internal.logging.aeri.ide.server.mars.ServerConnection.startUp(ServerConnection.java:124)
at com.google.common.util.concurrent.AbstractIdleService$2$1.run(AbstractIdleService.java:54)
at com.google.common.util.concurrent.Callables$3.run(Callables.java:93)
at java.lang.Thread.run(Thread.java:745)
!ENTRY org.teiid.designer.dqp 4 0 2017-03-02 09:49:24.542
!MESSAGE org.jboss.ide.eclipse.as.management.core.JBoss7ManangerException: org.jboss.ide.eclipse.as.management.core.JBoss7ManangerException: NLS missing message: OperationOnAddressFailed in: org.jboss.ide.eclipse.as.internal.management.wildfly9.Messages
!STACK 0
java.lang.Exception: org.jboss.ide.eclipse.as.management.core.JBoss7ManangerException: org.jboss.ide.eclipse.as.management.core.JBoss7ManangerException: NLS missing message: OperationOnAddressFailed in: org.jboss.ide.eclipse.as.internal.management.wildfly9.Messages
at org.teiid.designer.runtime.TeiidParentServerListener.adaptServerOK(TeiidParentServerListener.java:370)
at org.teiid.designer.runtime.TeiidParentServerListener.access$2(TeiidParentServerListener.java:363)
at org.teiid.designer.runtime.TeiidParentServerListener$1.tryConnecting(TeiidParentServerListener.java:291)
at org.teiid.designer.runtime.TeiidParentServerListener$1.run(TeiidParentServerListener.java:247)
at java.lang.Thread.run(Thread.java:745)
Caused by: org.jboss.ide.eclipse.as.management.core.JBoss7ManangerException: org.jboss.ide.eclipse.as.management.core.JBoss7ManangerException: NLS missing message: OperationOnAddressFailed in: org.jboss.ide.eclipse.as.internal.management.wildfly9.Messages
at org.jboss.ide.eclipse.as.internal.management.eap61plus.EAP61PlusManager.execute(EAP61PlusManager.java:361)
at org.jboss.ide.eclipse.as.internal.management.eap61plus.EAP61PlusManagerService.execute(EAP61PlusManagerService.java:171)
at org.jboss.ide.eclipse.as.management.core.JBoss7ManagerServiceProxy.execute(JBoss7ManagerServiceProxy.java:87)
at org.teiid.designer.runtime.adapter.JBoss7ServerUtil.executeRequest(JBoss7ServerUtil.java:78)
at org.teiid.designer.runtime.adapter.JBoss7ServerUtil.isTeiidServer(JBoss7ServerUtil.java:209)
at org.teiid.designer.runtime.adapter.TeiidServerAdapterFactory.adaptJBoss7Server(TeiidServerAdapterFactory.java:190)
at org.teiid.designer.runtime.adapter.TeiidServerAdapterFactory.adaptServer(TeiidServerAdapterFactory.java:89)
at org.teiid.designer.runtime.TeiidParentServerListener.adaptServerOK(TeiidParentServerListener.java:365)
... 4 more
Caused by: org.jboss.ide.eclipse.as.management.core.JBoss7ManangerException: NLS missing message: OperationOnAddressFailed in: org.jboss.ide.eclipse.as.internal.management.wildfly9.Messages
at org.jboss.ide.eclipse.as.internal.management.eap61plus.EAP61PlusManager.execute(EAP61PlusManager.java:352)
... 11 more
!ENTRY org.jboss.ide.eclipse.as.core 4 0 2017-03-02 09:49:29.910
!MESSAGE Unable to retrieve a list of remote deployment scanners for server Red Hat JBoss EAP 6.1+
!ENTRY org.jboss.ide.eclipse.as.core 4 0 2017-03-02 09:49:29.928
!MESSAGE Unable to retrieve a list of remote deployment scanners for server Red Hat JBoss EAP 6.1+
{code}
was:
Creating the SOAP war file usually works the first time if it's a brand new file, but if I need to regenerate the file for whatever reason, I have to attempt it 3 to 4 times before it will actually work. I thought it was something filesystem related, so after each failed attempt, I would refresh my project tree using the double refresh arrows, or I would right-click on the parent node and click refresh. If I'm lucky, it'll work right after the refresh trick, but it usually takes 3-4 times of trying before it finally takes.
This was also happening on JBDS 9.
> "Intialisation [sic] produced an exception" when starting Server
> ----------------------------------------------------------------
>
> Key: TEIIDDES-3051
> URL: https://issues.jboss.org/browse/TEIIDDES-3051
> Project: Teiid Designer
> Issue Type: Bug
> Affects Versions: 9.1, 10.1
> Environment: Windows 7, 64-bit
> JBoss Developer Studio 10.2.0.GA
> JBoss Data Virt Development (Teiid Designer) Integration Stack 10.1.0.GA
>
> Reporter: Steve Tran
> Attachments: Screenshot from 2017-03-02 10-00-08.png
>
>
> Starting the server always throws this exception. It's non-fatal, but it's been around since JBDS 8.
> Here's a snip from the logs.
> {code}
> !SESSION 2017-03-01 12:36:18.825 -----------------------------------------------
> eclipse.buildId=10.3.0.GA-v20170218-1636-B94
> java.version=1.8.0_121
> java.vendor=Oracle Corporation
> BootLoader constants: OS=win32, ARCH=x86_64, WS=win32, NL=en_US
> Framework arguments: -product com.jboss.devstudio.core.product
> Command-line arguments: -data file:/C:/Users/C031711/workspace/ -os win32 -ws win32 -arch x86_64 -product com.jboss.devstudio.core.product
> !ENTRY org.eclipse.egit.ui 2 0 2017-03-01 12:36:26.952
> !MESSAGE Warning: The environment variable HOME is not set. The following directory will be used to store the Git
> user global configuration and to define the default location to store repositories: 'C:\Users\C031711'. If this is
> not correct please set the HOME environment variable and restart Eclipse. Otherwise Git for Windows and
> EGit might behave differently since they see different configuration options.
> This warning can be switched off on the Team > Git > Confirmations and Warnings preference page.
> !ENTRY org.eclipse.epp.logging.aeri.ide 2 17 2017-03-01 12:36:27.847
> !MESSAGE Server ‘org.jboss.tools’ failed with exception: Proxy Unacknowledged. ; version: 2.0.3.v20161205-0933
> !STACK 0
> org.apache.http.client.HttpResponseException: Proxy Unacknowledged
> at org.eclipse.epp.internal.logging.aeri.ide.server.mars.HttpResponses$ProgressMonitorResponseHandler.handleResponse(HttpResponses.java:71)
> at org.eclipse.epp.internal.logging.aeri.ide.server.mars.HttpResponses$ProgressMonitorResponseStringHandler.handleResponse(HttpResponses.java:93)
> at org.eclipse.epp.internal.logging.aeri.ide.server.mars.HttpResponses$ProgressMonitorResponseStringHandler.handleResponse(HttpResponses.java:1)
> at org.apache.http.client.fluent.Response.handleResponse(Response.java:90)
> at org.eclipse.epp.internal.logging.aeri.ide.server.mars.HttpResponses.getContentWithProgress(HttpResponses.java:56)
> at org.eclipse.epp.internal.logging.aeri.ide.server.mars.IO.refreshConfiguration(IO.java:69)
> at org.eclipse.epp.internal.logging.aeri.ide.server.mars.ServerConnection.startUp(ServerConnection.java:124)
> at com.google.common.util.concurrent.AbstractIdleService$2$1.run(AbstractIdleService.java:54)
> at com.google.common.util.concurrent.Callables$3.run(Callables.java:93)
> at java.lang.Thread.run(Thread.java:745)
> !ENTRY org.teiid.designer.dqp 4 0 2017-03-02 09:49:24.542
> !MESSAGE org.jboss.ide.eclipse.as.management.core.JBoss7ManangerException: org.jboss.ide.eclipse.as.management.core.JBoss7ManangerException: NLS missing message: OperationOnAddressFailed in: org.jboss.ide.eclipse.as.internal.management.wildfly9.Messages
> !STACK 0
> java.lang.Exception: org.jboss.ide.eclipse.as.management.core.JBoss7ManangerException: org.jboss.ide.eclipse.as.management.core.JBoss7ManangerException: NLS missing message: OperationOnAddressFailed in: org.jboss.ide.eclipse.as.internal.management.wildfly9.Messages
> at org.teiid.designer.runtime.TeiidParentServerListener.adaptServerOK(TeiidParentServerListener.java:370)
> at org.teiid.designer.runtime.TeiidParentServerListener.access$2(TeiidParentServerListener.java:363)
> at org.teiid.designer.runtime.TeiidParentServerListener$1.tryConnecting(TeiidParentServerListener.java:291)
> at org.teiid.designer.runtime.TeiidParentServerListener$1.run(TeiidParentServerListener.java:247)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: org.jboss.ide.eclipse.as.management.core.JBoss7ManangerException: org.jboss.ide.eclipse.as.management.core.JBoss7ManangerException: NLS missing message: OperationOnAddressFailed in: org.jboss.ide.eclipse.as.internal.management.wildfly9.Messages
> at org.jboss.ide.eclipse.as.internal.management.eap61plus.EAP61PlusManager.execute(EAP61PlusManager.java:361)
> at org.jboss.ide.eclipse.as.internal.management.eap61plus.EAP61PlusManagerService.execute(EAP61PlusManagerService.java:171)
> at org.jboss.ide.eclipse.as.management.core.JBoss7ManagerServiceProxy.execute(JBoss7ManagerServiceProxy.java:87)
> at org.teiid.designer.runtime.adapter.JBoss7ServerUtil.executeRequest(JBoss7ServerUtil.java:78)
> at org.teiid.designer.runtime.adapter.JBoss7ServerUtil.isTeiidServer(JBoss7ServerUtil.java:209)
> at org.teiid.designer.runtime.adapter.TeiidServerAdapterFactory.adaptJBoss7Server(TeiidServerAdapterFactory.java:190)
> at org.teiid.designer.runtime.adapter.TeiidServerAdapterFactory.adaptServer(TeiidServerAdapterFactory.java:89)
> at org.teiid.designer.runtime.TeiidParentServerListener.adaptServerOK(TeiidParentServerListener.java:365)
> ... 4 more
> Caused by: org.jboss.ide.eclipse.as.management.core.JBoss7ManangerException: NLS missing message: OperationOnAddressFailed in: org.jboss.ide.eclipse.as.internal.management.wildfly9.Messages
> at org.jboss.ide.eclipse.as.internal.management.eap61plus.EAP61PlusManager.execute(EAP61PlusManager.java:352)
> ... 11 more
> !ENTRY org.jboss.ide.eclipse.as.core 4 0 2017-03-02 09:49:29.910
> !MESSAGE Unable to retrieve a list of remote deployment scanners for server Red Hat JBoss EAP 6.1+
> !ENTRY org.jboss.ide.eclipse.as.core 4 0 2017-03-02 09:49:29.928
> !MESSAGE Unable to retrieve a list of remote deployment scanners for server Red Hat JBoss EAP 6.1+
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 8 months
[JBoss JIRA] (TEIIDDES-3051) "Intialisation [sic] produced an exception" when starting Server
by Steve Tran (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-3051?page=com.atlassian.jira.plu... ]
Steve Tran updated TEIIDDES-3051:
---------------------------------
Steps to Reproduce:
1 - Open JBDS
2 - Start Server (assuming you have one already configured)
was:
1 - Build web-services.
2 - Add *-WS.xmi file to VDB
3 - Right-click to Create SOAP war
4 - Build SOAP war again, and choose to overwrite existing war file
> "Intialisation [sic] produced an exception" when starting Server
> ----------------------------------------------------------------
>
> Key: TEIIDDES-3051
> URL: https://issues.jboss.org/browse/TEIIDDES-3051
> Project: Teiid Designer
> Issue Type: Bug
> Affects Versions: 9.1, 10.1
> Environment: Windows 7, 64-bit
> JBoss Developer Studio 10.2.0.GA
> JBoss Data Virt Development (Teiid Designer) Integration Stack 10.1.0.GA
>
> Reporter: Steve Tran
>
> Creating the SOAP war file usually works the first time if it's a brand new file, but if I need to regenerate the file for whatever reason, I have to attempt it 3 to 4 times before it will actually work. I thought it was something filesystem related, so after each failed attempt, I would refresh my project tree using the double refresh arrows, or I would right-click on the parent node and click refresh. If I'm lucky, it'll work right after the refresh trick, but it usually takes 3-4 times of trying before it finally takes.
> This was also happening on JBDS 9.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 8 months
[JBoss JIRA] (TEIIDDES-3051) "Intialisation [sic] produced an exception" when starting Server
by Steve Tran (JIRA)
Steve Tran created TEIIDDES-3051:
------------------------------------
Summary: "Intialisation [sic] produced an exception" when starting Server
Key: TEIIDDES-3051
URL: https://issues.jboss.org/browse/TEIIDDES-3051
Project: Teiid Designer
Issue Type: Bug
Affects Versions: 9.1, 10.1
Environment: Windows 7, 64-bit
JBoss Developer Studio 10.2.0.GA
JBoss Data Virt Development (Teiid Designer) Integration Stack 10.1.0.GA
Reporter: Steve Tran
Creating the SOAP war file usually works the first time if it's a brand new file, but if I need to regenerate the file for whatever reason, I have to attempt it 3 to 4 times before it will actually work. I thought it was something filesystem related, so after each failed attempt, I would refresh my project tree using the double refresh arrows, or I would right-click on the parent node and click refresh. If I'm lucky, it'll work right after the refresh trick, but it usually takes 3-4 times of trying before it finally takes.
This was also happening on JBDS 9.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 8 months
[JBoss JIRA] (TEIIDDES-2559) Load and saving non-workspace vdb fails to retain udf jars and other files
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2559?page=com.atlassian.jira.plu... ]
Barry LaFond updated TEIIDDES-2559:
-----------------------------------
Fix Version/s: (was: 9.2.1)
(was: 10.0)
> Load and saving non-workspace vdb fails to retain udf jars and other files
> --------------------------------------------------------------------------
>
> Key: TEIIDDES-2559
> URL: https://issues.jboss.org/browse/TEIIDDES-2559
> Project: Teiid Designer
> Issue Type: Bug
> Components: Patch Release, VDB & Execution
> Affects Versions: 9.0.2
> Reporter: Paul Richardson
> Assignee: Paul Richardson
> Fix For: 11.2
>
> Attachments: UdfVdb.vdb
>
>
> Vdbs that contain either udf libaries or 'other files' are prone to losing these files when edited in Designer.
> This only occurs if the vdb is not part of a project, in that its constituent files are not part of the workspace.
> When such a vdb is opened by the editor, the archive is extracted to the staging area and the metadata loaded into the in-memory model. The vdb can be edited and saved.
> However, the save results in the udf jars and 'other files' not being included in the updated archive.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 8 months
[JBoss JIRA] (TEIIDDES-2990) Strange behaviour with multi-sources in dynamic VDB
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2990?page=com.atlassian.jira.plu... ]
Barry LaFond updated TEIIDDES-2990:
-----------------------------------
Fix Version/s: 11.0.2
(was: 11.0.1)
> Strange behaviour with multi-sources in dynamic VDB
> ---------------------------------------------------
>
> Key: TEIIDDES-2990
> URL: https://issues.jboss.org/browse/TEIIDDES-2990
> Project: Teiid Designer
> Issue Type: Bug
> Components: Dynamic VDBs, Import/Export
> Affects Versions: 10.0.2
> Reporter: Mario Majernik
> Assignee: Barry LaFond
> Fix For: 11.0.2
>
> Attachments: ModelSourceVDB-vdb.xml
>
>
> Line 9 and 10 in dynamic VDB describe two sources.
> When you generate static VDB and check Source binding tab there is just one source model.
> He has Source name from line 9 but translator name and JNDI name from line 10.
> Also "Add Column" checkbox is not check.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 8 months
[JBoss JIRA] (TEIIDDES-2958) Missing property when I want to edit infinispan-cache-dsl translator
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2958?page=com.atlassian.jira.plu... ]
Barry LaFond updated TEIIDDES-2958:
-----------------------------------
Fix Version/s: 11.0.2
> Missing property when I want to edit infinispan-cache-dsl translator
> --------------------------------------------------------------------
>
> Key: TEIIDDES-2958
> URL: https://issues.jboss.org/browse/TEIIDDES-2958
> Project: Teiid Designer
> Issue Type: Bug
> Affects Versions: 10.0.2
> Reporter: Matej Kralik
> Assignee: Barry LaFond
> Priority: Minor
> Fix For: 11.0.2
>
> Attachments: screenshot1.png, screenshot2.png
>
>
> According to [this |https://issues.jboss.org/browse/TEIIDDES-2812?focusedCommentId=13283715&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-13283715] comment, when I click on the JDG source model and I want to override translator, SupportsDirectQueryProcedure parameter is missing. (screenshot1)
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 8 months
[JBoss JIRA] (TEIIDDES-2958) Missing property when I want to edit infinispan-cache-dsl translator
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2958?page=com.atlassian.jira.plu... ]
Barry LaFond reassigned TEIIDDES-2958:
--------------------------------------
Assignee: Barry LaFond
> Missing property when I want to edit infinispan-cache-dsl translator
> --------------------------------------------------------------------
>
> Key: TEIIDDES-2958
> URL: https://issues.jboss.org/browse/TEIIDDES-2958
> Project: Teiid Designer
> Issue Type: Bug
> Affects Versions: 10.0.2
> Reporter: Matej Kralik
> Assignee: Barry LaFond
> Priority: Minor
> Fix For: 11.0.2
>
> Attachments: screenshot1.png, screenshot2.png
>
>
> According to [this |https://issues.jboss.org/browse/TEIIDDES-2812?focusedCommentId=13283715&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-13283715] comment, when I click on the JDG source model and I want to override translator, SupportsDirectQueryProcedure parameter is missing. (screenshot1)
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 8 months
[JBoss JIRA] (TEIIDDES-2964) Add capability to set a default data role grant
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2964?page=com.atlassian.jira.plu... ]
Barry LaFond updated TEIIDDES-2964:
-----------------------------------
Fix Version/s: 11.0.2
> Add capability to set a default data role grant
> -----------------------------------------------
>
> Key: TEIIDDES-2964
> URL: https://issues.jboss.org/browse/TEIIDDES-2964
> Project: Teiid Designer
> Issue Type: Feature Request
> Components: VDB & Execution
> Reporter: Debbie Steigner
> Assignee: Barry LaFond
> Priority: Minor
> Fix For: 11.0.2
>
>
> We use JDV as "data-firewall", so there are a lot of groups configured on JDV data roles section.
> Each time we add a model object to the project, by default all read permission are granted to that model for all groups.
> We think it could be better, to have an option in the "Data Roles" tab, avoiding users to uncheck for all the groups's permission which aren't needed (see page 2 attachment JDV_RFE_security_default_profile).
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 8 months