[JBoss JIRA] (WFLY-6312) Intermittent failure: client gets NPE in ejbremote scenario
by Michal Vinkler (JIRA)
Michal Vinkler created WFLY-6312:
------------------------------------
Summary: Intermittent failure: client gets NPE in ejbremote scenario
Key: WFLY-6312
URL: https://issues.jboss.org/browse/WFLY-6312
Project: WildFly
Issue Type: Bug
Components: Clustering
Reporter: Michal Vinkler
Assignee: Paul Ferraro
Seen in a scenario: ejb-ejbremote-shutdown-repl-async
Approx. 20 seconds after perf18 was restarted (after previous graceful shutdown), client logged thi NPE seven times. No error occurred on any of the servers during that time.
{code}
2016/02/25 19:23:11:869 EST [ERROR][Runner - 633] HOST perf17.mw.lab.eng.bos.redhat.com:rootProcess:c - Error getting response. <java.lang.NullPointerException>
java.lang.NullPointerException
at org.jboss.remoting3.remote.OutboundMessage$2.getKey(OutboundMessage.java:173)
at org.jboss.remoting3.remote.OutboundMessage$2.getKey(OutboundMessage.java:171)
at org.jboss.remoting3.remote.IntIndexHashMap.doGet(IntIndexHashMap.java:507)
at org.jboss.remoting3.remote.IntIndexHashMap.containsKey(IntIndexHashMap.java:169)
at org.jboss.remoting3.remote.RemoteConnectionChannel.writeMessage(RemoteConnectionChannel.java:313)
at org.jboss.ejb.client.remoting.ChannelAssociation.acquireChannelMessageOutputStream(ChannelAssociation.java:281)
at org.jboss.ejb.client.remoting.RemotingConnectionEJBReceiver.processInvocationInternal(RemotingConnectionEJBReceiver.java:295)
at org.jboss.ejb.client.remoting.RemotingConnectionEJBReceiver.access$100(RemotingConnectionEJBReceiver.java:77)
at org.jboss.ejb.client.remoting.RemotingConnectionEJBReceiver$2.run(RemotingConnectionEJBReceiver.java:282)
at java.security.AccessController.doPrivileged(Native Method)
at org.jboss.ejb.client.remoting.RemotingConnectionEJBReceiver.processInvocation(RemotingConnectionEJBReceiver.java:279)
at org.jboss.ejb.client.EJBClientInvocationContext.sendRequest(EJBClientInvocationContext.java:184)
at org.jboss.ejb.client.EJBObjectInterceptor.handleInvocation(EJBObjectInterceptor.java:58)
at org.jboss.ejb.client.EJBClientInvocationContext.sendRequest(EJBClientInvocationContext.java:186)
at org.jboss.ejb.client.EJBHomeInterceptor.handleInvocation(EJBHomeInterceptor.java:83)
at org.jboss.ejb.client.EJBClientInvocationContext.sendRequest(EJBClientInvocationContext.java:186)
at org.jboss.ejb.client.TransactionInterceptor.handleInvocation(TransactionInterceptor.java:42)
at org.jboss.ejb.client.EJBClientInvocationContext.sendRequest(EJBClientInvocationContext.java:186)
at org.jboss.ejb.client.ReceiverInterceptor.handleInvocation(ReceiverInterceptor.java:138)
at org.jboss.ejb.client.EJBClientInvocationContext.sendRequest(EJBClientInvocationContext.java:186)
at org.jboss.ejb.client.EJBInvocationHandler.sendRequestWithPossibleRetries(EJBInvocationHandler.java:255)
at org.jboss.ejb.client.EJBInvocationHandler.doInvoke(EJBInvocationHandler.java:200)
at org.jboss.ejb.client.EJBInvocationHandler.doInvoke(EJBInvocationHandler.java:183)
at org.jboss.ejb.client.EJBInvocationHandler.invoke(EJBInvocationHandler.java:146)
at com.sun.proxy.$Proxy2.getSerialAndIncrement(Unknown Source)
at org.jboss.smartfrog.clustering.ejb3.StatefulSBProcessorFactoryImpl$EJB3RequestProcessor.processRequest(StatefulSBProcessorFactoryImpl.java:84)
at org.jboss.smartfrog.loaddriver.CompoundRequestProcessorFactoryImpl$CompoundRequestProcessor.processRequest(CompoundRequestProcessorFactoryImpl.java:52)
at org.jboss.smartfrog.loaddriver.Runner.run(Runner.java:103)
at java.lang.Thread.run(Thread.java:745)
{code}
Client link:
http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/eap-7x-failover-ejb-e...
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (WFLY-6312) Intermittent failure: client gets NPE in ejbremote scenario
by Michal Vinkler (JIRA)
[ https://issues.jboss.org/browse/WFLY-6312?page=com.atlassian.jira.plugin.... ]
Michal Vinkler updated WFLY-6312:
---------------------------------
Affects Version/s: 10.0.0.Final
> Intermittent failure: client gets NPE in ejbremote scenario
> -------------------------------------------------------------
>
> Key: WFLY-6312
> URL: https://issues.jboss.org/browse/WFLY-6312
> Project: WildFly
> Issue Type: Bug
> Components: Clustering
> Affects Versions: 10.0.0.Final
> Reporter: Michal Vinkler
> Assignee: Paul Ferraro
>
> Seen in a scenario: ejb-ejbremote-shutdown-repl-async
> Approx. 20 seconds after perf18 was restarted (after previous graceful shutdown), client logged thi NPE seven times. No error occurred on any of the servers during that time.
> {code}
> 2016/02/25 19:23:11:869 EST [ERROR][Runner - 633] HOST perf17.mw.lab.eng.bos.redhat.com:rootProcess:c - Error getting response. <java.lang.NullPointerException>
> java.lang.NullPointerException
> at org.jboss.remoting3.remote.OutboundMessage$2.getKey(OutboundMessage.java:173)
> at org.jboss.remoting3.remote.OutboundMessage$2.getKey(OutboundMessage.java:171)
> at org.jboss.remoting3.remote.IntIndexHashMap.doGet(IntIndexHashMap.java:507)
> at org.jboss.remoting3.remote.IntIndexHashMap.containsKey(IntIndexHashMap.java:169)
> at org.jboss.remoting3.remote.RemoteConnectionChannel.writeMessage(RemoteConnectionChannel.java:313)
> at org.jboss.ejb.client.remoting.ChannelAssociation.acquireChannelMessageOutputStream(ChannelAssociation.java:281)
> at org.jboss.ejb.client.remoting.RemotingConnectionEJBReceiver.processInvocationInternal(RemotingConnectionEJBReceiver.java:295)
> at org.jboss.ejb.client.remoting.RemotingConnectionEJBReceiver.access$100(RemotingConnectionEJBReceiver.java:77)
> at org.jboss.ejb.client.remoting.RemotingConnectionEJBReceiver$2.run(RemotingConnectionEJBReceiver.java:282)
> at java.security.AccessController.doPrivileged(Native Method)
> at org.jboss.ejb.client.remoting.RemotingConnectionEJBReceiver.processInvocation(RemotingConnectionEJBReceiver.java:279)
> at org.jboss.ejb.client.EJBClientInvocationContext.sendRequest(EJBClientInvocationContext.java:184)
> at org.jboss.ejb.client.EJBObjectInterceptor.handleInvocation(EJBObjectInterceptor.java:58)
> at org.jboss.ejb.client.EJBClientInvocationContext.sendRequest(EJBClientInvocationContext.java:186)
> at org.jboss.ejb.client.EJBHomeInterceptor.handleInvocation(EJBHomeInterceptor.java:83)
> at org.jboss.ejb.client.EJBClientInvocationContext.sendRequest(EJBClientInvocationContext.java:186)
> at org.jboss.ejb.client.TransactionInterceptor.handleInvocation(TransactionInterceptor.java:42)
> at org.jboss.ejb.client.EJBClientInvocationContext.sendRequest(EJBClientInvocationContext.java:186)
> at org.jboss.ejb.client.ReceiverInterceptor.handleInvocation(ReceiverInterceptor.java:138)
> at org.jboss.ejb.client.EJBClientInvocationContext.sendRequest(EJBClientInvocationContext.java:186)
> at org.jboss.ejb.client.EJBInvocationHandler.sendRequestWithPossibleRetries(EJBInvocationHandler.java:255)
> at org.jboss.ejb.client.EJBInvocationHandler.doInvoke(EJBInvocationHandler.java:200)
> at org.jboss.ejb.client.EJBInvocationHandler.doInvoke(EJBInvocationHandler.java:183)
> at org.jboss.ejb.client.EJBInvocationHandler.invoke(EJBInvocationHandler.java:146)
> at com.sun.proxy.$Proxy2.getSerialAndIncrement(Unknown Source)
> at org.jboss.smartfrog.clustering.ejb3.StatefulSBProcessorFactoryImpl$EJB3RequestProcessor.processRequest(StatefulSBProcessorFactoryImpl.java:84)
> at org.jboss.smartfrog.loaddriver.CompoundRequestProcessorFactoryImpl$CompoundRequestProcessor.processRequest(CompoundRequestProcessorFactoryImpl.java:52)
> at org.jboss.smartfrog.loaddriver.Runner.run(Runner.java:103)
> at java.lang.Thread.run(Thread.java:745)
> {code}
> Client link:
> http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/eap-7x-failover-ejb-e...
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (WFLY-5995) Initial calculation of the first expiration time for a scheduled timer is wrong if a start date is set
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/WFLY-5995?page=com.atlassian.jira.plugin.... ]
RH Bugzilla Integration commented on WFLY-5995:
-----------------------------------------------
Jiří Bílek <jbilek(a)redhat.com> changed the Status of [bug 1298651|https://bugzilla.redhat.com/show_bug.cgi?id=1298651] from ON_QA to VERIFIED
> Initial calculation of the first expiration time for a scheduled timer is wrong if a start date is set
> ------------------------------------------------------------------------------------------------------
>
> Key: WFLY-5995
> URL: https://issues.jboss.org/browse/WFLY-5995
> Project: WildFly
> Issue Type: Bug
> Components: EJB
> Affects Versions: 8.2.1.Final, 9.0.2.Final, 10.0.0.CR5
> Reporter: Wolf-Dieter Fink
> Assignee: Wolf-Dieter Fink
> Labels: timers, timerservice
> Fix For: 10.0.0.Final
>
>
> If a scheduled timer should be created with the following parameters:
> ScheduleExpression[second=0 minute=0/5 hour=20-22 dayOfWeek=* dayOfMonth=* month=* year=* start=Thu Jan 14 09:45:35 GMT+1 2016]
> The first schedule should be
> Thu Jan 17 20:00:20 GMT+1 2016
> but is calculated as
> Sun Jan 17 20:45:35 GMT+1 2016
> The minutes are not correctly set according to the schedule and the given start date.
> This happen for seconds/minutes if the ScheduleExpression limit the range.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (JBJCA-1310) NPE when validating database connection (and the validation failed) if connection pool statistics is enabled
by Jesper Pedersen (JIRA)
[ https://issues.jboss.org/browse/JBJCA-1310?page=com.atlassian.jira.plugin... ]
Jesper Pedersen updated JBJCA-1310:
-----------------------------------
Fix Version/s: WildFly/IronJacamar 1.3.3.Final
1.2.7.Final
Priority: Blocker (was: Critical)
> NPE when validating database connection (and the validation failed) if connection pool statistics is enabled
> ------------------------------------------------------------------------------------------------------------
>
> Key: JBJCA-1310
> URL: https://issues.jboss.org/browse/JBJCA-1310
> Project: IronJacamar
> Issue Type: Bug
> Components: Core
> Affects Versions: WildFly/IronJacamar 1.3.2.Final, 1.2.6.Final
> Reporter: Hugh Nguyen
> Assignee: Jesper Pedersen
> Priority: Blocker
> Fix For: WildFly/IronJacamar 1.3.3.Final, 1.2.7.Final
>
> Attachments: ironjacamar-core-impl.jar, server_orig.log, server_patch.log
>
>
> - An xa-datasource connection pool is configured with: statistic-enabled=true, validate-on-match=true
> - When validation failed, after the failure, the following is logged:
> {code}
> 2016-02-10 12:23:12,580 WARN [org.jboss.jca.core.connectionmanager.pool.strategy.OnePool] (Sched1_Worker-13) IJ000621: Destroying connection that could not be validated: null
> {code}
> - This appears to come from SemaphoreConcurrentLinkedDequeManagedConnectionPool.java, line 436:
> {code}
> log.destroyingConnectionNotValidated(clw.getConnectionListener());
> {code}
> - So apparently clw.getConnectionListener() is null at this point, causing line 441/442 to throw NPE, if statistics is enabled:
> {code}
> pool.getInternalStatistics().deltaTotalPoolTime(lastUsed - clw.getConnectionListener().getLastReturnedTime());
> {code}
> - NPE is caught by the catch clause, and line 456 write the following to the log:
> {code}
> 2016-02-10 12:23:12,580 WARN [org.jboss.jca.core.connectionmanager.pool.strategy.OnePool] (Sched1_Worker-13) IJ000613: Throwable while trying to match managed connection, destroying connection: null: java.lang.NullPointerException
> at org.jboss.jca.core.connectionmanager.pool.mcp.SemaphoreConcurrentLinkedDequeManagedConnectionPool.getConnection(SemaphoreConcurrentLinkedDequeManagedConnectionPool.java:441)
> at org.jboss.jca.core.connectionmanager.pool.AbstractPool.getTransactionNewConnection(AbstractPool.java:708)
> at org.jboss.jca.core.connectionmanager.pool.AbstractPool.getConnection(AbstractPool.java:607)
> at org.jboss.jca.core.connectionmanager.AbstractConnectionManager.getManagedConnection(AbstractConnectionManager.java:590)
> at org.jboss.jca.core.connectionmanager.tx.TxConnectionManagerImpl.getManagedConnection(TxConnectionManagerImpl.java:429)
> at org.jboss.jca.core.connectionmanager.AbstractConnectionManager.allocateConnection(AbstractConnectionManager.java:747)
> {code}
> - However, this catch clause try to do the same thing that cause the NPE in line 461/462
> {code}
> pool.getInternalStatistics().deltaTotalPoolTime(lastUsed - clw.getConnectionListener().getLastReturnedTime());
> {code}
> - And finally this NPE is throw all the way out to the user of the connection
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (DROOLS-1078) Drools can incorrectly generate Java code to access a method on a wrong reference type for a covariant return
by Juan Carlos Garcia (JIRA)
[ https://issues.jboss.org/browse/DROOLS-1078?page=com.atlassian.jira.plugi... ]
Juan Carlos Garcia updated DROOLS-1078:
---------------------------------------
Attachment: bug.patch
I think i nailed the problem to the drools-core/src/main/java/org/drools/core/util/asm/ClassFieldInspector.java
In the attached patch file you will find a testcase to reproduce the problem and the suggested fix for it.
> Drools can incorrectly generate Java code to access a method on a wrong reference type for a covariant return
> -------------------------------------------------------------------------------------------------------------
>
> Key: DROOLS-1078
> URL: https://issues.jboss.org/browse/DROOLS-1078
> Project: Drools
> Issue Type: Bug
> Affects Versions: 6.2.0.Final, 6.3.0.Final
> Reporter: Juan Carlos Garcia
> Assignee: Mark Proctor
> Attachments: bug.patch, DroolsBugDemo.zip
>
>
> Drools will incorrectly generate Java code to access a method on a wrong reference type, hence resulting in a rule compilation error.
> Taking the following rule as example (which is also attached),
> {code}
> import bug.demo.Table;
> import bug.demo.Constants;
> import bug.demo.Player;
> import bug.demo.event.GenericEvent;
> import bug.demo.api.model.Card;
> rule "BuggyRule"
> when
> $discardCardEvent : GenericEvent(eventName=="fooEvent",
> $discardedCard : Card.fromMap(getEventProperty("fooCard")),
> Constants.FOO_RANK.contains($discardedCard.getRank()),
> $playerIndex : slotIndex) from entry-point "foo-stream"
> $table : Table($currentPlayer : getCurrentPlayer())
> then
> $table.addToDiscardPile($discardedCard);
> $table.reset();
> $currentPlayer.removeCard($discardedCard);
> end
> {code}
> In this case when compiling the following rule, we may end up (sometimes) with compilation error:
> *The method removeCard(Card) is undefined for the type TurnbasedPlayer* , when a Player type should be used in first place.
> Attached is sample project to reproduce the problem, be aware that you may need to do *mvn clean test* several times until you actually trigger the problem, if you are lucky enough it will get trigger the first time you execute it.
> Environment:
> {code}
> >mvn -version
> Apache Maven 3.2.5 (12a6b3acb947671f09b81f49094c53f426d8cea1; 2014-12-14T18:29:23+01:00)
> Maven home: /usr/share/maven
> Java version: 1.7.0_79, vendor: Oracle Corporation
> Java home: /usr/lib/jvm/jdk-7-oracle-x64/jre
> Default locale: en_US, platform encoding: UTF-8
> OS name: "linux", version: "3.13.0-77-generic", arch: "amd64", family: "unix"
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (WFLY-2948) Welcome file does not work for *.jsf
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/WFLY-2948?page=com.atlassian.jira.plugin.... ]
RH Bugzilla Integration commented on WFLY-2948:
-----------------------------------------------
Michael Cada <mcada(a)redhat.com> changed the Status of [bug 1256325|https://bugzilla.redhat.com/show_bug.cgi?id=1256325] from ON_QA to VERIFIED
> Welcome file does not work for *.jsf
> --------------------------------------
>
> Key: WFLY-2948
> URL: https://issues.jboss.org/browse/WFLY-2948
> Project: WildFly
> Issue Type: Bug
> Components: Web (Undertow)
> Affects Versions: 8.0.0.Final
> Reporter: Gulam Samdani
> Assignee: Remy Maucherat
> Priority: Minor
> Fix For: 8.1.0.CR1, 8.1.0.Final
>
>
> Welcome file does not work for *.jsf
> --------------------------------------------------------
> same problem not exists in Wildfly Beta but wildfly 8 final /cr1 gives this error ...
>
> problem :
>
> http://localhost:8080/hello ------------------------------ NO works***
> @http://localhost:8080/hello/index.jsf ------------- it works fine
> =======================================
> <welcome-file-list>
>
> <welcome-file>index.jsf</welcome-file>
>
> </welcome-file-list>
> <servlet>
> <servlet-name>Faces Servlet</servlet-name>
> <servlet-class>javax.faces.webapp.FacesServlet</servlet-class>
> <load-on-startup>1</load-on-startup>
> </servlet>
> <servlet-mapping>
> <servlet-name>Faces Servlet</servlet-name>
> <url-pattern>*.jsf</url-pattern>
> </servlet-mapping>
> </web-app>
> -------------------------------------------------
> Reproduce this error :
> https://community.jboss.org/message/857300
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (JBJCA-1310) NPE when validating database connection (and the validation failed) if connection pool statistics is enabled
by Martin Simka (JIRA)
[ https://issues.jboss.org/browse/JBJCA-1310?page=com.atlassian.jira.plugin... ]
Martin Simka updated JBJCA-1310:
--------------------------------
Attachment: server_patch.log
server_orig.log
it can be reproduced by
{code}
xa-data-source add --name=TestXADS --jndi-name=java:jboss/datasources/TestXADS --driver-name=h2 --validate-on-match=true --statistics-enabled=true --valid-connection-checker-class-name="org.jboss.jca.adapters.jdbc.extensions.novendor.SQLExceptionValidConnectionChecker" --xa-datasource-class="org.h2.jdbcx.JdbcDataSource" --user-name=sa --password=sa --min-pool-size=1 --max-pool-size=1 --pool-prefill=true --xa-datasource-properties=URL=jdbc:h2:mem:test;DB_CLOSE_DELAY=-1;DB_CLOSE_ON_EXIT=FALSE
/subsystem=datasources/xa-data-source=TestXADS:test-connection-in-pool
{code}
logs attached, _patch is with ironjacamar-core-impl.jar from this jira
> NPE when validating database connection (and the validation failed) if connection pool statistics is enabled
> ------------------------------------------------------------------------------------------------------------
>
> Key: JBJCA-1310
> URL: https://issues.jboss.org/browse/JBJCA-1310
> Project: IronJacamar
> Issue Type: Bug
> Components: Core
> Affects Versions: WildFly/IronJacamar 1.3.2.Final, 1.2.6.Final
> Reporter: Hugh Nguyen
> Assignee: Jesper Pedersen
> Priority: Critical
> Attachments: ironjacamar-core-impl.jar, server_orig.log, server_patch.log
>
>
> - An xa-datasource connection pool is configured with: statistic-enabled=true, validate-on-match=true
> - When validation failed, after the failure, the following is logged:
> {code}
> 2016-02-10 12:23:12,580 WARN [org.jboss.jca.core.connectionmanager.pool.strategy.OnePool] (Sched1_Worker-13) IJ000621: Destroying connection that could not be validated: null
> {code}
> - This appears to come from SemaphoreConcurrentLinkedDequeManagedConnectionPool.java, line 436:
> {code}
> log.destroyingConnectionNotValidated(clw.getConnectionListener());
> {code}
> - So apparently clw.getConnectionListener() is null at this point, causing line 441/442 to throw NPE, if statistics is enabled:
> {code}
> pool.getInternalStatistics().deltaTotalPoolTime(lastUsed - clw.getConnectionListener().getLastReturnedTime());
> {code}
> - NPE is caught by the catch clause, and line 456 write the following to the log:
> {code}
> 2016-02-10 12:23:12,580 WARN [org.jboss.jca.core.connectionmanager.pool.strategy.OnePool] (Sched1_Worker-13) IJ000613: Throwable while trying to match managed connection, destroying connection: null: java.lang.NullPointerException
> at org.jboss.jca.core.connectionmanager.pool.mcp.SemaphoreConcurrentLinkedDequeManagedConnectionPool.getConnection(SemaphoreConcurrentLinkedDequeManagedConnectionPool.java:441)
> at org.jboss.jca.core.connectionmanager.pool.AbstractPool.getTransactionNewConnection(AbstractPool.java:708)
> at org.jboss.jca.core.connectionmanager.pool.AbstractPool.getConnection(AbstractPool.java:607)
> at org.jboss.jca.core.connectionmanager.AbstractConnectionManager.getManagedConnection(AbstractConnectionManager.java:590)
> at org.jboss.jca.core.connectionmanager.tx.TxConnectionManagerImpl.getManagedConnection(TxConnectionManagerImpl.java:429)
> at org.jboss.jca.core.connectionmanager.AbstractConnectionManager.allocateConnection(AbstractConnectionManager.java:747)
> {code}
> - However, this catch clause try to do the same thing that cause the NPE in line 461/462
> {code}
> pool.getInternalStatistics().deltaTotalPoolTime(lastUsed - clw.getConnectionListener().getLastReturnedTime());
> {code}
> - And finally this NPE is throw all the way out to the user of the connection
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (DROOLS-1079) Kie navigator cannot show organizational units content
by Tomas David (JIRA)
[ https://issues.jboss.org/browse/DROOLS-1079?page=com.atlassian.jira.plugi... ]
Tomas David updated DROOLS-1079:
--------------------------------
Priority: Critical (was: Major)
> Kie navigator cannot show organizational units content
> ------------------------------------------------------
>
> Key: DROOLS-1079
> URL: https://issues.jboss.org/browse/DROOLS-1079
> Project: Drools
> Issue Type: Bug
> Components: eclipse plugin
> Environment: JBoss Developer Studio 9.1.0.Beta2
> Drools plugin 6.4.0.201601201107
> Reporter: Tomas David
> Assignee: Robert (Bob) Brodt
> Priority: Critical
> Labels: reported-by-qe
>
> It is not possible to open organizational units and display associated repositories. Also when you create a new repository in org unit, it is not displayed in kie navigator but in business central app it is correctly created.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (DROOLS-1079) Kie navigator cannot show organizational units content
by Tomas David (JIRA)
[ https://issues.jboss.org/browse/DROOLS-1079?page=com.atlassian.jira.plugi... ]
Tomas David updated DROOLS-1079:
--------------------------------
Description: It is not possible to open organizational units and display associated repositories. Also when you create a new repository in org unit, it is not displayed in kie navigator but in business central app it is correctly created. (was: It is not possible to open organizational units and display associated repositories. Also when you create a new repository in org unit, it is not displayed in kie navigator but in business central app is correctly created.)
> Kie navigator cannot show organizational units content
> ------------------------------------------------------
>
> Key: DROOLS-1079
> URL: https://issues.jboss.org/browse/DROOLS-1079
> Project: Drools
> Issue Type: Bug
> Components: eclipse plugin
> Environment: JBoss Developer Studio 9.1.0.Beta2
> Drools plugin 6.4.0.201601201107
> Reporter: Tomas David
> Assignee: Robert (Bob) Brodt
> Labels: reported-by-qe
>
> It is not possible to open organizational units and display associated repositories. Also when you create a new repository in org unit, it is not displayed in kie navigator but in business central app it is correctly created.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month