[JBoss JIRA] (DROOLS-1214) SEVERE: TransactionSynchronization.beforeCompletion threw exception javax.persistence.PersistenceException: org.hibernate.exception.GenericJDBCException: could not update: [org.drools.persistence.info.SessionInfo#1]
by Michael Anstis (JIRA)
[ https://issues.jboss.org/browse/DROOLS-1214?page=com.atlassian.jira.plugi... ]
Michael Anstis moved GUVNOR-2567 to DROOLS-1214:
------------------------------------------------
Project: Drools (was: Guvnor)
Key: DROOLS-1214 (was: GUVNOR-2567)
Issue Type: Bug (was: Feature Request)
Workflow: GIT Pull Request workflow (was: classic default workflow)
Affects Version/s: (was: drools_6.4.0.Final)
Fix Version/s: (was: drools_6.4.0.Final)
> SEVERE: TransactionSynchronization.beforeCompletion threw exception javax.persistence.PersistenceException: org.hibernate.exception.GenericJDBCException: could not update: [org.drools.persistence.info.SessionInfo#1]
> -----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: DROOLS-1214
> URL: https://issues.jboss.org/browse/DROOLS-1214
> Project: Drools
> Issue Type: Bug
> Reporter: Chitta Khatua
>
> This is the complete Error :
> javax.persistence.PersistenceException: org.hibernate.exception.GenericJDBCException: could not update: [org.drools.persistence.info.SessionInfo#1]
> at org.hibernate.ejb.AbstractEntityManagerImpl.convert(AbstractEntityManagerImpl.java:1387)
> at org.hibernate.ejb.AbstractEntityManagerImpl.convert(AbstractEntityManagerImpl.java:1310)
>
>
> Caused by: org.hibernate.exception.GenericJDBCException: could not update: [org.drools.persistence.info.SessionInfo#1]
> at org.hibernate.exception.internal.StandardSQLExceptionConverter.convert(StandardSQLExceptionConverter.java:54)
> at org.hibernate.engine.jdbc.spi.SqlExceptionHelper.convert(SqlExceptionHelper.java:125)
> at org.hibernate.persister.entity.AbstractEntityPersister.update(AbstractEntityPersister.java:3237)
>
> Caused by: org.postgresql.util.PSQLException: Large Objects may not be used in auto-commit mode.
> at org.postgresql.largeobject.LargeObjectManager.createLO(LargeObjectManager.java:308)
> at org.postgresql.largeobject.LargeObjectManager.createLO(LargeObjectManager.java:296)
>
> java.lang.IllegalStateException: java.lang.reflect.InvocationTargetException
> at org.drools.persistence.jpa.KnowledgeStoreServiceImpl.buildCommandService(KnowledgeStoreServiceImpl.java:185)
> at org.drools.persistence.jpa.KnowledgeStoreServiceImpl.newKieSession(KnowledgeStoreServiceImpl.java:70)
> at org.drools.persistence.jpa.KnowledgeStoreServiceImpl.newKieSession(KnowledgeStoreServiceImpl.java:39)
> Caused by: java.lang.reflect.InvocationTargetException
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
> at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)
> Caused by: java.lang.RuntimeException: Could not commit session or rollback
> at org.drools.persistence.SingleSessionCommandService.rollbackTransaction(SingleSessionCommandService.java:405)
> at org.drools.persistence.SingleSessionCommandService.rollbackTransaction(SingleSessionCommandService.java:389)
>
> Caused by: java.lang.RuntimeException: Unable to rollback transaction
> at org.kie.spring.persistence.KieSpringTransactionManager.rollback(KieSpringTransactionManager.java:90)
>
> Caused by: org.springframework.transaction.IllegalTransactionStateException: Transaction is already completed - do not call commit or rollback more than once per transaction
> at org.springframework.transaction.support.AbstractPlatformTransactionManager.rollback(AbstractPlatformTransactionManager.java:825)
> at org.kie.spring.persistence.KieSpringTransactionManager.rollback(KieSpringTransactionManager.java:84)
> ------------------------------------------------------------------------------------------
> jbpm-manager.xml
> -----------------------
> <beans xmlns="http://www.springframework.org/schema/beans"
> xmlns:context="http://www.springframework.org/schema/context"
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
> xmlns:util="http://www.springframework.org/schema/util"
> xsi:schemaLocation="
> http://www.springframework.org/schema/beans
> http://www.springframework.org/schema/beans/spring-beans-3.0.xsd
> http://www.springframework.org/schema/context
> http://www.springframework.org/schema/context/spring-context-3.0.xsd
> http://www.springframework.org/schema/util http://www.springframework.org/schema/util/spring-util.xsd">
> <bean id="jbpmEMF" class="org.springframework.orm.jpa.LocalContainerEntityManagerFactoryBean">
> <property name="persistenceUnitName" value="org.jbpm.persistence.spring.jta"/>
> <!-- property name="persistenceUnitName" value="org.jbpm.persistence.jpa"/>-->
> <property name="persistenceXmlLocation" value="classpath:jbpm/persistence-jta.xml"/>
> <!-- property name="dataSource" ref="jbpmDS" />-->
> </bean>
>
> <!-- bean id="jbpmDS" class="bitronix.tm.resource.jdbc.PoolingDataSource" init-method="init" destroy-method="close">
> <property name="className" value="org.postgresql.xa.PGXADataSource" />
> <property name="uniqueName" value="jbpmDS" />
> <property name="minPoolSize" value="0" />
> <property name="maxPoolSize" value="20" />
> <property name="allowLocalTransactions" value="true" />
> <property name="testQuery" value="SELECT 1 FROM DUAL" />-->
> <!--property name="ignoreRecoveryFailures" value="true" /-->
> <!--property name="driverProperties">
> <props>
> <prop key="serverName">localhost</prop>
> <prop key="databaseName">noesis</prop>
> <prop key="user">postgres</prop>
> <prop key="password">postgres</prop>
> </props>
> </property>
> </bean>-->
>
> <bean id="btmConfig" factory-method="getConfiguration" class="bitronix.tm.TransactionManagerServices"></bean>
>
> <bean id="BitronixTransactionManager" factory-method="getTransactionManager"
> class="bitronix.tm.TransactionManagerServices" depends-on="btmConfig" destroy-method="shutdown" />
>
> <bean id="jbpmTxManager" class="org.springframework.transaction.jta.JtaTransactionManager">
> <property name="transactionManager" ref="BitronixTransactionManager" />
> <property name="userTransaction" ref="BitronixTransactionManager" />
> </bean>
> <bean id="process" factory-method="newClassPathResource" class="org.kie.internal.io.ResourceFactory">
> <constructor-arg>
> <value>test.bpmn</value>
> </constructor-arg>
> </bean>
> <bean id="runtimeEnvironment" class="org.kie.spring.factorybeans.RuntimeEnvironmentFactoryBean">
> <property name="type" value="DEFAULT"/>
> <property name="entityManagerFactory" ref="jbpmEMF"/>
> <property name="transactionManager" ref="jbpmTxManager"/>
> <property name="assets">
> <map>
> <entry key-ref="process"><util:constant static-field="org.kie.api.io.ResourceType.BPMN2"/></entry>
> </map>
> </property>
> </bean>
> <bean id="runtimeManager" class="org.kie.spring.factorybeans.RuntimeManagerFactoryBean" destroy-method="close">
> <property name="identifier" value="spring-rm"/>
> <property name="runtimeEnvironment" ref="runtimeEnvironment"/>
> </bean>
> </beans>
> ------------------------------------------------------------------------
> kmodule.xml
> ---------------------
> <kmodule xmlns="http://jboss.org/kie/6.0.0/kmodule">
> <kbase name="kbase" packages="org.jbpm.demo" />
> </kmodule>
> -------------------------------------------------------------------------------
> persistence-jta.xml
> -----------------------
> <?xml version="1.0" encoding="UTF-8"?>
> <persistence
> version="2.0"
> xmlns="http://java.sun.com/xml/ns/persistence"
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
> xsi:schemaLocation="http://java.sun.com/xml/ns/persistence http://java.sun.com/xml/ns/persistence/persistence_2_0.xsd">
> <!-- spring with jta -->
> <persistence-unit name="org.jbpm.persistence.spring.jta" transaction-type="JTA">
> <!-- persistence-unit name="org.jbpm.persistence.jpa" transaction-type="JTA">-->
> <provider>org.hibernate.ejb.HibernatePersistence</provider>
> <!-- jta-data-source>java:comp/env/jdbc/jbpm-ds</jta-data-source>-->
> <!--<mapping-file>META-INF/JBPMorm.xml</mapping-file>-->
> <mapping-file>META-INF/Taskorm.xml</mapping-file>
> <mapping-file>META-INF/TaskAuditorm.xml</mapping-file>
> <class>org.jbpm.persistence.processinstance.ProcessInstanceInfo</class>
> <class>org.drools.persistence.info.SessionInfo</class>
> <class>org.drools.persistence.info.WorkItemInfo</class>
> <class>org.jbpm.process.audit.ProcessInstanceLog</class>
> <class>org.jbpm.process.audit.NodeInstanceLog</class>
> <class>org.jbpm.process.audit.VariableInstanceLog</class>
> <class>org.jbpm.persistence.correlation.CorrelationKeyInfo</class>
> <class>org.jbpm.persistence.correlation.CorrelationPropertyInfo</class>
> <!-- manager -->
> <class>org.jbpm.runtime.manager.impl.jpa.ContextMappingInfo</class>
> <class>org.jbpm.services.task.impl.model.AttachmentImpl</class>
> <class>org.jbpm.services.task.impl.model.ContentImpl</class>
> <class>org.jbpm.services.task.impl.model.BooleanExpressionImpl</class>
> <class>org.jbpm.services.task.impl.model.CommentImpl</class>
> <class>org.jbpm.services.task.impl.model.DeadlineImpl</class>
> <class>org.jbpm.services.task.impl.model.CommentImpl</class>
> <class>org.jbpm.services.task.impl.model.DeadlineImpl</class>
> <class>org.jbpm.services.task.impl.model.DelegationImpl</class>
> <class>org.jbpm.services.task.impl.model.EscalationImpl</class>
> <class>org.jbpm.services.task.impl.model.GroupImpl</class>
> <class>org.jbpm.services.task.impl.model.I18NTextImpl</class>
> <class>org.jbpm.services.task.impl.model.NotificationImpl</class>
> <class>org.jbpm.services.task.impl.model.EmailNotificationImpl</class>
> <class>org.jbpm.services.task.impl.model.EmailNotificationHeaderImpl</class>
> <class>org.jbpm.services.task.impl.model.PeopleAssignmentsImpl</class>
> <class>org.jbpm.services.task.impl.model.ReassignmentImpl</class>
> <class>org.jbpm.services.task.impl.model.TaskImpl</class>
> <class>org.jbpm.services.task.impl.model.TaskDataImpl</class>
> <class>org.jbpm.services.task.impl.model.UserImpl</class>
> <!--BAM for task service -->
> <class>org.jbpm.services.task.audit.impl.model.BAMTaskSummaryImpl</class>
> <class>org.jbpm.services.task.audit.impl.model.TaskEventImpl</class>
> <!-- Task Audit Classes -->
> <class>org.jbpm.services.task.audit.impl.model.AuditTaskImpl</class>
> <class>org.jbpm.services.task.audit.impl.model.TaskVariableImpl</class>
>
> <properties>
> <property name="hibernate.max_fetch_depth" value="3"/>
> <property name="hibernate.hbm2ddl.auto" value="create" />
> <property name="hibernate.show_sql" value="true" />
> <!-- property name="hibernate.dialect" value="org.hibernate.dialect.H2Dialect"/-->
> <property name="hibernate.dialect" value="org.hibernate.dialect.PostgreSQL82Dialect"/>
> <property name="hibernate.connection.driver_class" value="org.postgresql.Driver"/>
> <property name="hibernate.connection.username" value="postgres"/>
> <property name="hibernate.connection.password" value="postgres"/>
> <property name="hibernate.connection.url" value="jdbc:postgresql://localhost:5432/noesis"/>
>
> <!-- BZ 841786: AS7/EAP 6/Hib 4 uses new (sequence) generators which seem to cause problems -->
> <property name="hibernate.id.new_generator_mappings" value="false" />
> <property name="hibernate.transaction.jta.platform" value="org.hibernate.service.jta.platform.internal.BitronixJtaPlatform" />
> </properties>
> </persistence-unit>
> </persistence>
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (WFLY-6734) Server should expose information about available modules
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFLY-6734?page=com.atlassian.jira.plugin.... ]
Brian Stansberry updated WFLY-6734:
-----------------------------------
Description:
It would be great if server exposed information about available modules.
*Example of usage:*
* Run WildFly
* go to Configuration -> Subsystems -> Infinispan
* pick any cache container
* click on Add
-Set module can not be verified right now, therefore user may set wrong module without noticing.- Moreover there could be some helper for available modules.
was:
It would be great if server exposed information about available modules.
*Example of usage:*
* Run WildFly
* go to Configuration -> Subsystems -> Infinispan
* pick any cache container
* click on Add
Set module can not be verified right now, therefore user may set wrong module without noticing. Moreover there could be some helper for available modules.
> Server should expose information about available modules
> --------------------------------------------------------
>
> Key: WFLY-6734
> URL: https://issues.jboss.org/browse/WFLY-6734
> Project: WildFly
> Issue Type: Feature Request
> Components: Server
> Reporter: Ivan Straka
> Priority: Minor
>
> It would be great if server exposed information about available modules.
> *Example of usage:*
> * Run WildFly
> * go to Configuration -> Subsystems -> Infinispan
> * pick any cache container
> * click on Add
> -Set module can not be verified right now, therefore user may set wrong module without noticing.- Moreover there could be some helper for available modules.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (WFCORE-1608) Server should expose information about available modules
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFCORE-1608?page=com.atlassian.jira.plugi... ]
Brian Stansberry moved WFLY-6734 to WFCORE-1608:
------------------------------------------------
Project: WildFly Core (was: WildFly)
Key: WFCORE-1608 (was: WFLY-6734)
Component/s: Domain Management
(was: Server)
Fix Version/s: (was: 10.0.0.Final)
> Server should expose information about available modules
> --------------------------------------------------------
>
> Key: WFCORE-1608
> URL: https://issues.jboss.org/browse/WFCORE-1608
> Project: WildFly Core
> Issue Type: Feature Request
> Components: Domain Management
> Reporter: Ivan Straka
> Priority: Minor
>
> It would be great if server exposed information about available modules.
> *Example of usage:*
> * Run WildFly
> * go to Configuration -> Subsystems -> Infinispan
> * pick any cache container
> * click on Add
> -Set module can not be verified right now, therefore user may set wrong module without noticing.- Moreover there could be some helper for available modules.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (WFLY-6734) Server should expose information about available modules
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFLY-6734?page=com.atlassian.jira.plugin.... ]
Brian Stansberry reopened WFLY-6734:
------------------------------------
Assignee: (was: Tomaz Cerar)
I'm reopening because the WFCORE-570 module-info op shows the info about a provided module name, but that doesn't allow the user to see available modules. We do expose this via JMX but that doesn't help the console.
I'll move this to WFCORE as it's a kernel feature being requested.
> Server should expose information about available modules
> --------------------------------------------------------
>
> Key: WFLY-6734
> URL: https://issues.jboss.org/browse/WFLY-6734
> Project: WildFly
> Issue Type: Feature Request
> Components: Server
> Reporter: Ivan Straka
> Priority: Minor
> Fix For: 10.0.0.Final
>
>
> It would be great if server exposed information about available modules.
> *Example of usage:*
> * Run WildFly
> * go to Configuration -> Subsystems -> Infinispan
> * pick any cache container
> * click on Add
> Set module can not be verified right now, therefore user may set wrong module without noticing. Moreover there could be some helper for available modules.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (WFLY-6747) messaging subsystem bridge fails on differents Ip orders
by Radoslav Husar (JIRA)
[ https://issues.jboss.org/browse/WFLY-6747?page=com.atlassian.jira.plugin.... ]
Radoslav Husar reassigned WFLY-6747:
------------------------------------
Component/s: JMS
(was: Clustering)
Assignee: Jeff Mesnil (was: Paul Ferraro)
> messaging subsystem bridge fails on differents Ip orders
> --------------------------------------------------------
>
> Key: WFLY-6747
> URL: https://issues.jboss.org/browse/WFLY-6747
> Project: WildFly
> Issue Type: Bug
> Components: JMS
> Affects Versions: 8.2.0.Final
> Environment: Wildfly 8.2.0.Final domain mode. 2 Hosts each one with one server, one contains also the domain controller. Verified on Windows and on Linux (AWS machines).
> Reporter: Lorenzo Pirazzini
> Assignee: Jeff Mesnil
>
> While trying to setup a clustered environment with Wildfly 8.2.0.Final I needed a shared topic between servers (I have two Linux machines on AWS).
> Everything works fine (domain creation, datasources/persistence unit, infinispan shared caches and Wildfly Console) except for HornetQ messaging subsystem.
> I can't use discovery because I don't have a multicast address, so I defined a *domain.xml* like this:
> <subsystem xmlns="urn:jboss:domain:messaging:2.0">
> <hornetq-server>
> <cluster-password>myPassword</cluster-password>
> <backup>false</backup>
> <shared-store>false</shared-store>
> <journal-file-size>102400</journal-file-size>
> <connectors>
> <http-connector name="http-connector" socket-binding="http">
> <param key="http-upgrade-endpoint" value="http-acceptor"/>
> </http-connector>
> <http-connector name="http-connector-throughput" socket-binding="http">
> <param key="http-upgrade-endpoint" value="http-acceptor-throughput"/>
> <param key="batch-delay" value="50"/>
> </http-connector>
> <http-connector name="cnode1" socket-binding="node1">
> <param key="http-upgrade-endpoint" value="http-acceptor"/>
> </http-connector>
> <http-connector name="cnode2" socket-binding="node2">
> <param key="http-upgrade-endpoint" value="http-acceptor"/>
> </http-connector>
> <in-vm-connector name="in-vm" server-id="0"/>
> </connectors>
> <acceptors>
> <http-acceptor http-listener="default" name="http-acceptor"/>
> <http-acceptor http-listener="default" name="http-acceptor-throughput">
> <param key="batch-delay" value="50"/>
> <param key="direct-deliver" value="false"/>
> </http-acceptor>
> <in-vm-acceptor name="in-vm" server-id="0"/>
> </acceptors>
> <cluster-connections>
> <cluster-connection name="my-cluster">
> <address>jms</address>
> <connector-ref>http-connector</connector-ref>
> <static-connectors>
> <connector-ref>
> cnode1
> </connector-ref>
> <connector-ref>
> cnode2
> </connector-ref>
> </static-connectors>
> </cluster-connection>
> </cluster-connections>
> <security-settings>
> <security-setting match="#">
> <permission type="send" roles="guest"/>
> <permission type="consume" roles="guest"/>
> <permission type="createNonDurableQueue" roles="guest"/>
> <permission type="deleteNonDurableQueue" roles="guest"/>
> </security-setting>
> </security-settings>
> <address-settings>
> <address-setting match="#">
> <dead-letter-address>jms.queue.DLQ</dead-letter-address>
> <expiry-address>jms.queue.ExpiryQueue</expiry-address>
> <max-size-bytes>10485760</max-size-bytes>
> <page-size-bytes>2097152</page-size-bytes>
> <message-counter-history-day-limit>10</message-counter-history-day-limit>
> <redistribution-delay>1000</redistribution-delay>
> </address-setting>
> </address-settings>
> <jms-connection-factories>
> <connection-factory name="InVmConnectionFactory">
> <connectors>
> <connector-ref connector-name="in-vm"/>
> </connectors>
> <entries>
> <entry name="java:/ConnectionFactory"/>
> </entries>
> </connection-factory>
> <connection-factory name="RemoteConnectionFactory">
> <connectors>
> <connector-ref connector-name="http-connector"/>
> </connectors>
> <entries>
> <entry name="java:jboss/exported/jms/RemoteConnectionFactory"/>
> </entries>
> <ha>true</ha>
> <block-on-acknowledge>true</block-on-acknowledge>
> <reconnect-attempts>-1</reconnect-attempts>
> </connection-factory>
> <pooled-connection-factory name="hornetq-ra">
> <transaction mode="xa"/>
> <connectors>
> <connector-ref connector-name="in-vm"/>
> </connectors>
> <entries>
> <entry name="java:/JmsXA"/>
> <entry name="java:jboss/DefaultJMSConnectionFactory"/>
> </entries>
> </pooled-connection-factory>
> </jms-connection-factories>
> <jms-destinations>
> ...
> <jms-topic name="MyTopic">
> <entry name="java:/jms/topic/MyTopic"/>
> </jms-topic>
> ...
> </jms-destinations>
> </hornetq-server>
> </subsystem>
> ...
> <socket-binding-group name="full-ha-sockets" default-interface="public">
> <socket-binding name="ajp" port="${jboss.ajp.port:8009}"/>
> <socket-binding name="http" port="${jboss.http.port:8080}"/>
> <socket-binding name="https" port="${jboss.https.port:8443}"/>
> <socket-binding name="jacorb" interface="unsecure" port="3528"/>
> <socket-binding name="jacorb-ssl" interface="unsecure" port="3529"/>
> <socket-binding name="jgroups-mping" port="0" multicast-address="${jboss.default.multicast.address:230.0.0.4}" multicast-port="45700"/>
> <socket-binding name="jgroups-tcp" port="7600"/>
> <socket-binding name="jgroups-tcp-fd" port="57600"/>
> <socket-binding name="jgroups-udp" port="55200" multicast-address="${jboss.default.multicast.address:230.0.0.4}" multicast-port="45688"/>
> <socket-binding name="jgroups-udp-fd" port="54200"/>
> <socket-binding name="messaging-group" port="0" multicast-address="${jboss.messaging.group.address:231.7.7.7}" multicast-port="${jboss.messaging.group.port:9876}"/>
> <socket-binding name="txn-recovery-environment" port="4712"/>
> <socket-binding name="txn-status-manager" port="4713"/>
> <outbound-socket-binding name="mail-smtp">
> <remote-destination host="localhost" port="25"/>
> </outbound-socket-binding>
> <outbound-socket-binding name="node1">
> <remote-destination host="IP-A" port="8080"/>
> </outbound-socket-binding>
> <outbound-socket-binding name="node2">
> <remote-destination host="IP-B" port="8080"/>
> </outbound-socket-binding>
> </socket-binding-group>
> </socket-binding-groups>
> where IP-A is the Ip of the host with domain controller and a server, and IP-B is the address of the host with only a server instance.
> If I invert those two IPs HornetQ doesn't create the bridge! The topic isn't shared, every message is processed only by the topic owned by the current server.
> Why the order of sucjh addresses determines the correct behaviour of the messaging subsystem? I haven't found anything useful on the documentation, am I missing something??
> This is the line which is written only in the order proposed which starts the HornetQ shared topics:
> 2016-06-20 12:18:17,943 INFO [org.hornetq.core.server] (Thread-29 (HornetQ-server-HornetQServerImpl::serverUUID=ead3e226-2c7c-11e6-81c9-1fb90d688ead-2097612799)) HQ221027: Bridge ClusterConnectionBridge@4862c348 [name=sf.my-cluster.25728e77-2c02-11e6-8d49-3995f9ecf159, queue=QueueImpl[name=sf.my-cluster.25728e77-2c02-11e6-8d49-3995f9ecf159, postOffice=PostOfficeImpl [server=HornetQServerImpl::serverUUID=ead3e226-2c7c-11e6-81c9-1fb90d688ead]]@4ceda5a4 targetConnector=ServerLocatorImpl (identity=(Cluster-connection-bridge::ClusterConnectionBridge@4862c348 [name=sf.my-cluster.25728e77-2c02-11e6-8d49-3995f9ecf159, queue=QueueImpl[name=sf.my-cluster.25728e77-2c02-11e6-8d49-3995f9ecf159, postOffice=PostOfficeImpl [server=HornetQServerImpl::serverUUID=ead3e226-2c7c-11e6-81c9-1fb90d688ead]]@4ceda5a4 targetConnector=ServerLocatorImpl [initialConnectors=[TransportConfiguration(name=http-connector, factory=org-hornetq-core-remoting-impl-netty-NettyConnectorFactory) ?port=8080&http-upgrade-endpoint=http-acceptor&host=IP_B&http-upgrade-enabled=true], discoveryGroupConfiguration=null]]::ClusterConnectionImpl@1383156397[nodeUUID=ead3e226-2c7c-11e6-81c9-1fb90d688ead, connector=TransportConfiguration(name=http-connector, factory=org-hornetq-core-remoting-impl-netty-NettyConnectorFactory) ?port=8080&host=IP-A&http-upgrade-endpoint=http-acceptor&http-upgrade-enabled=true, address=jms, server=HornetQServerImpl::serverUUID=ead3e226-2c7c-11e6-81c9-1fb90d688ead])) [initialConnectors=[TransportConfiguration(name=http-connector, factory=org-hornetq-core-remoting-impl-netty-NettyConnectorFactory) ?port=8080&http-upgrade-endpoint=http-acceptor&host=IP-B&http-upgrade-enabled=true], discoveryGroupConfiguration=null]] is connected
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (WFLY-6747) messaging subsystem bridge fails on differents Ip orders
by Lorenzo Pirazzini (JIRA)
Lorenzo Pirazzini created WFLY-6747:
---------------------------------------
Summary: messaging subsystem bridge fails on differents Ip orders
Key: WFLY-6747
URL: https://issues.jboss.org/browse/WFLY-6747
Project: WildFly
Issue Type: Bug
Components: Clustering
Affects Versions: 8.2.0.Final
Environment: Wildfly 8.2.0.Final domain mode. 2 Hosts each one with one server, one contains also the domain controller. Verified on Windows and on Linux (AWS machines).
Reporter: Lorenzo Pirazzini
Assignee: Paul Ferraro
While trying to setup a clustered environment with Wildfly 8.2.0.Final I needed a shared topic between servers (I have two Linux machines on AWS).
Everything works fine (domain creation, datasources/persistence unit, infinispan shared caches and Wildfly Console) except for HornetQ messaging subsystem.
I can't use discovery because I don't have a multicast address, so I defined a *domain.xml* like this:
<subsystem xmlns="urn:jboss:domain:messaging:2.0">
<hornetq-server>
<cluster-password>myPassword</cluster-password>
<backup>false</backup>
<shared-store>false</shared-store>
<journal-file-size>102400</journal-file-size>
<connectors>
<http-connector name="http-connector" socket-binding="http">
<param key="http-upgrade-endpoint" value="http-acceptor"/>
</http-connector>
<http-connector name="http-connector-throughput" socket-binding="http">
<param key="http-upgrade-endpoint" value="http-acceptor-throughput"/>
<param key="batch-delay" value="50"/>
</http-connector>
<http-connector name="cnode1" socket-binding="node1">
<param key="http-upgrade-endpoint" value="http-acceptor"/>
</http-connector>
<http-connector name="cnode2" socket-binding="node2">
<param key="http-upgrade-endpoint" value="http-acceptor"/>
</http-connector>
<in-vm-connector name="in-vm" server-id="0"/>
</connectors>
<acceptors>
<http-acceptor http-listener="default" name="http-acceptor"/>
<http-acceptor http-listener="default" name="http-acceptor-throughput">
<param key="batch-delay" value="50"/>
<param key="direct-deliver" value="false"/>
</http-acceptor>
<in-vm-acceptor name="in-vm" server-id="0"/>
</acceptors>
<cluster-connections>
<cluster-connection name="my-cluster">
<address>jms</address>
<connector-ref>http-connector</connector-ref>
<static-connectors>
<connector-ref>
cnode1
</connector-ref>
<connector-ref>
cnode2
</connector-ref>
</static-connectors>
</cluster-connection>
</cluster-connections>
<security-settings>
<security-setting match="#">
<permission type="send" roles="guest"/>
<permission type="consume" roles="guest"/>
<permission type="createNonDurableQueue" roles="guest"/>
<permission type="deleteNonDurableQueue" roles="guest"/>
</security-setting>
</security-settings>
<address-settings>
<address-setting match="#">
<dead-letter-address>jms.queue.DLQ</dead-letter-address>
<expiry-address>jms.queue.ExpiryQueue</expiry-address>
<max-size-bytes>10485760</max-size-bytes>
<page-size-bytes>2097152</page-size-bytes>
<message-counter-history-day-limit>10</message-counter-history-day-limit>
<redistribution-delay>1000</redistribution-delay>
</address-setting>
</address-settings>
<jms-connection-factories>
<connection-factory name="InVmConnectionFactory">
<connectors>
<connector-ref connector-name="in-vm"/>
</connectors>
<entries>
<entry name="java:/ConnectionFactory"/>
</entries>
</connection-factory>
<connection-factory name="RemoteConnectionFactory">
<connectors>
<connector-ref connector-name="http-connector"/>
</connectors>
<entries>
<entry name="java:jboss/exported/jms/RemoteConnectionFactory"/>
</entries>
<ha>true</ha>
<block-on-acknowledge>true</block-on-acknowledge>
<reconnect-attempts>-1</reconnect-attempts>
</connection-factory>
<pooled-connection-factory name="hornetq-ra">
<transaction mode="xa"/>
<connectors>
<connector-ref connector-name="in-vm"/>
</connectors>
<entries>
<entry name="java:/JmsXA"/>
<entry name="java:jboss/DefaultJMSConnectionFactory"/>
</entries>
</pooled-connection-factory>
</jms-connection-factories>
<jms-destinations>
...
<jms-topic name="MyTopic">
<entry name="java:/jms/topic/MyTopic"/>
</jms-topic>
...
</jms-destinations>
</hornetq-server>
</subsystem>
...
<socket-binding-group name="full-ha-sockets" default-interface="public">
<socket-binding name="ajp" port="${jboss.ajp.port:8009}"/>
<socket-binding name="http" port="${jboss.http.port:8080}"/>
<socket-binding name="https" port="${jboss.https.port:8443}"/>
<socket-binding name="jacorb" interface="unsecure" port="3528"/>
<socket-binding name="jacorb-ssl" interface="unsecure" port="3529"/>
<socket-binding name="jgroups-mping" port="0" multicast-address="${jboss.default.multicast.address:230.0.0.4}" multicast-port="45700"/>
<socket-binding name="jgroups-tcp" port="7600"/>
<socket-binding name="jgroups-tcp-fd" port="57600"/>
<socket-binding name="jgroups-udp" port="55200" multicast-address="${jboss.default.multicast.address:230.0.0.4}" multicast-port="45688"/>
<socket-binding name="jgroups-udp-fd" port="54200"/>
<socket-binding name="messaging-group" port="0" multicast-address="${jboss.messaging.group.address:231.7.7.7}" multicast-port="${jboss.messaging.group.port:9876}"/>
<socket-binding name="txn-recovery-environment" port="4712"/>
<socket-binding name="txn-status-manager" port="4713"/>
<outbound-socket-binding name="mail-smtp">
<remote-destination host="localhost" port="25"/>
</outbound-socket-binding>
<outbound-socket-binding name="node1">
<remote-destination host="IP-A" port="8080"/>
</outbound-socket-binding>
<outbound-socket-binding name="node2">
<remote-destination host="IP-B" port="8080"/>
</outbound-socket-binding>
</socket-binding-group>
</socket-binding-groups>
where IP-A is the Ip of the host with domain controller and a server, and IP-B is the address of the host with only a server instance.
If I invert those two IPs HornetQ doesn't create the bridge! The topic isn't shared, every message is processed only by the topic owned by the current server.
Why the order of sucjh addresses determines the correct behaviour of the messaging subsystem? I haven't found anything useful on the documentation, am I missing something??
This is the line which is written only in the order proposed which starts the HornetQ shared topics:
2016-06-20 12:18:17,943 INFO [org.hornetq.core.server] (Thread-29 (HornetQ-server-HornetQServerImpl::serverUUID=ead3e226-2c7c-11e6-81c9-1fb90d688ead-2097612799)) HQ221027: Bridge ClusterConnectionBridge@4862c348 [name=sf.my-cluster.25728e77-2c02-11e6-8d49-3995f9ecf159, queue=QueueImpl[name=sf.my-cluster.25728e77-2c02-11e6-8d49-3995f9ecf159, postOffice=PostOfficeImpl [server=HornetQServerImpl::serverUUID=ead3e226-2c7c-11e6-81c9-1fb90d688ead]]@4ceda5a4 targetConnector=ServerLocatorImpl (identity=(Cluster-connection-bridge::ClusterConnectionBridge@4862c348 [name=sf.my-cluster.25728e77-2c02-11e6-8d49-3995f9ecf159, queue=QueueImpl[name=sf.my-cluster.25728e77-2c02-11e6-8d49-3995f9ecf159, postOffice=PostOfficeImpl [server=HornetQServerImpl::serverUUID=ead3e226-2c7c-11e6-81c9-1fb90d688ead]]@4ceda5a4 targetConnector=ServerLocatorImpl [initialConnectors=[TransportConfiguration(name=http-connector, factory=org-hornetq-core-remoting-impl-netty-NettyConnectorFactory) ?port=8080&http-upgrade-endpoint=http-acceptor&host=IP_B&http-upgrade-enabled=true], discoveryGroupConfiguration=null]]::ClusterConnectionImpl@1383156397[nodeUUID=ead3e226-2c7c-11e6-81c9-1fb90d688ead, connector=TransportConfiguration(name=http-connector, factory=org-hornetq-core-remoting-impl-netty-NettyConnectorFactory) ?port=8080&host=IP-A&http-upgrade-endpoint=http-acceptor&http-upgrade-enabled=true, address=jms, server=HornetQServerImpl::serverUUID=ead3e226-2c7c-11e6-81c9-1fb90d688ead])) [initialConnectors=[TransportConfiguration(name=http-connector, factory=org-hornetq-core-remoting-impl-netty-NettyConnectorFactory) ?port=8080&http-upgrade-endpoint=http-acceptor&host=IP-B&http-upgrade-enabled=true], discoveryGroupConfiguration=null]] is connected
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (DROOLS-1212) Input stream finalized or forced closed during server startup
by Fernando Machado (JIRA)
Fernando Machado created DROOLS-1212:
----------------------------------------
Summary: Input stream finalized or forced closed during server startup
Key: DROOLS-1212
URL: https://issues.jboss.org/browse/DROOLS-1212
Project: Drools
Issue Type: Bug
Components: core engine
Affects Versions: 6.3.0.Final
Environment: Glassfish 4.1.1
Reporter: Fernando Machado
Assignee: Mario Fusco
I'm getting some exceptions during GF4 startup related with _"Input stream has been finalized or forced closed without being explicitly closed; stream instantiation reported in following stack trace"_ and it seems similar to DROOLS-812.
org.drools.template.parser.DefaultTemplateRuleBase.readKnowledgeBase(String)
{code}
private InternalKnowledgeBase readKnowledgeBase(String drl) {
try {
// logger.info(drl);
// read in the source
Reader source = new StringReader(drl);
KnowledgeBuilderImpl builder = new KnowledgeBuilderImpl();
builder.addPackageFromDrl(source);
InternalKnowledgePackage pkg = builder.getPackage();
// add the package to a rulebase (deploy the rule package).
InternalKnowledgeBase kBase = (InternalKnowledgeBase) KnowledgeBaseFactory.newKnowledgeBase();
kBase.addPackage(pkg);
return kBase;
} catch (Exception e) {
throw new RuntimeException(e);
}
}
{code}
Is related with:
{noformat}
[#|2016-06-15T13:51:07.671+0200|WARNING|glassfish 4.1|javax.enterprise.system.util|_ThreadID=74442;_ThreadName=RunLevelControllerThread-1465991462855;_TimeMillis=1465991467671;_LevelValue=900;_MessageID=NCLS-COMUTIL-00023;|Input stream has been finalized or forced closed without being explicitly closed; stream instantiation reported in following stack trace
java.lang.Throwable
at org.drools.template.parser.DefaultTemplateRuleBase.readKnowledgeBase(DefaultTemplateRuleBase.java:133)
at org.drools.template.parser.DefaultTemplateRuleBase.<init>(DefaultTemplateRuleBase.java:56)
at org.drools.template.parser.TemplateDataListener.<init>(TemplateDataListener.java:74)
at org.drools.template.parser.TemplateDataListener.<init>(TemplateDataListener.java:50)
at org.drools.template.ObjectDataCompiler.compile(ObjectDataCompiler.java:57)
at com.mycompany.mypackage.MyClass.init(MyClass.java:xxx)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at com.sun.ejb.containers.interceptors.BeanCallbackInterceptor.intercept(InterceptorManager.java:1035)
at com.sun.ejb.containers.interceptors.CallbackChainImpl.invokeNext(CallbackChainImpl.java:72)
at com.sun.ejb.containers.interceptors.CallbackInvocationContext.proceed(CallbackInvocationContext.java:205)
at org.jboss.weld.ejb.AbstractEJBRequestScopeActivationInterceptor.aroundInvoke(AbstractEJBRequestScopeActivationInterceptor.java:73)
at org.jboss.weld.ejb.SessionBeanInterceptor.aroundInvoke(SessionBeanInterceptor.java:52)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at com.sun.ejb.containers.interceptors.CallbackInterceptor.intercept(InterceptorManager.java:986)
at com.sun.ejb.containers.interceptors.CallbackChainImpl.invokeNext(CallbackChainImpl.java:72)
at com.sun.ejb.containers.interceptors.CallbackInvocationContext.proceed(CallbackInvocationContext.java:205)
at com.sun.ejb.containers.interceptors.SystemInterceptorProxy.doCall(SystemInterceptorProxy.java:163)
at com.sun.ejb.containers.interceptors.SystemInterceptorProxy.init(SystemInterceptorProxy.java:125)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at com.sun.ejb.containers.interceptors.CallbackInterceptor.intercept(InterceptorManager.java:986)
at com.sun.ejb.containers.interceptors.CallbackChainImpl.invokeNext(CallbackChainImpl.java:72)
at com.sun.ejb.containers.interceptors.InterceptorManager.intercept(InterceptorManager.java:412)
at com.sun.ejb.containers.interceptors.InterceptorManager.intercept(InterceptorManager.java:375)
at com.sun.ejb.containers.BaseContainer.intercept(BaseContainer.java:2014)
at com.sun.ejb.containers.AbstractSingletonContainer.createSingletonEJB(AbstractSingletonContainer.java:468)
at com.sun.ejb.containers.AbstractSingletonContainer.access$000(AbstractSingletonContainer.java:74)
at com.sun.ejb.containers.AbstractSingletonContainer$SingletonContextFactory.create(AbstractSingletonContainer.java:647)
at com.sun.ejb.containers.AbstractSingletonContainer.instantiateSingletonInstance(AbstractSingletonContainer.java:389)
at org.glassfish.ejb.startup.SingletonLifeCycleManager.initializeSingleton(SingletonLifeCycleManager.java:219)
at org.glassfish.ejb.startup.SingletonLifeCycleManager.initializeSingleton(SingletonLifeCycleManager.java:180)
at org.glassfish.ejb.startup.SingletonLifeCycleManager.doStartup(SingletonLifeCycleManager.java:158)
...
{noformat}
There is another class that is also throwing the same exception:
{noformat}
[#|2016-06-14T11:08:19.953+0200|WARNING|glassfish 4.1|javax.enterprise.system.util|_ThreadID=68093;_ThreadName=RunLevelControllerThread-1465895294550;_TimeMillis=1465895299953;_LevelValue=900;_MessageID=NCLS-COMUTIL-00023;|Input stream has been finalized or forced closed without being explicitly closed;
stream instantiation reported in following stack trace
java.lang.Throwable
at com.sun.enterprise.loader.ASURLClassLoader$SentinelInputStream.<init>(ASURLClassLoader.java:1278)
at com.sun.enterprise.loader.ASURLClassLoader$InternalJarURLConnection.getInputStream(ASURLClassLoader.java:1386)
at java.net.URLClassLoader.getResourceAsStream(URLClassLoader.java:238)
at com.sun.enterprise.loader.ASURLClassLoader.getResourceAsStream(ASURLClassLoader.java:930)
at java.lang.Class.getResourceAsStream(Class.java:2223)
at org.eclipse.jdt.internal.compiler.parser.Parser.readReadableNameTable(Parser.java:719)
at org.eclipse.jdt.internal.compiler.parser.Parser.initTables(Parser.java:615)
at org.eclipse.jdt.internal.compiler.parser.Parser.<clinit>(Parser.java:124)
at org.eclipse.jdt.internal.compiler.Compiler.initializeParser(Compiler.java:687)
at org.eclipse.jdt.internal.compiler.Compiler.<init>(Compiler.java:285)
at org.eclipse.jdt.internal.compiler.Compiler.<init>(Compiler.java:206)
at org.drools.compiler.commons.jci.compilers.EclipseJavaCompiler.compile(EclipseJavaCompiler.java:416)
at org.drools.compiler.commons.jci.compilers.AbstractJavaCompiler.compile(AbstractJavaCompiler.java:49)
at org.drools.compiler.rule.builder.dialect.java.JavaDialect.compileAll(JavaDialect.java:417)
at org.drools.compiler.compiler.DialectCompiletimeRegistry.compileAll(DialectCompiletimeRegistry.java:61)
at org.drools.compiler.compiler.PackageRegistry.compileAll(PackageRegistry.java:138)
at org.drools.compiler.builder.impl.KnowledgeBuilderImpl.compileAll(KnowledgeBuilderImpl.java:1314)
at org.drools.compiler.builder.impl.KnowledgeBuilderImpl.compileAllRules(KnowledgeBuilderImpl.java:953)
at org.drools.compiler.builder.impl.KnowledgeBuilderImpl.addPackage(KnowledgeBuilderImpl.java:944)
at org.drools.compiler.builder.impl.KnowledgeBuilderImpl.addPackageFromDrl(KnowledgeBuilderImpl.java:363)
at org.drools.compiler.builder.impl.KnowledgeBuilderImpl.addPackageFromDrl(KnowledgeBuilderImpl.java:339)
at org.drools.template.parser.DefaultTemplateRuleBase.readKnowledgeBase(DefaultTemplateRuleBase.java:133)
at org.drools.template.parser.DefaultTemplateRuleBase.<init>(DefaultTemplateRuleBase.java:56)
at org.drools.template.parser.TemplateDataListener.<init>(TemplateDataListener.java:74)
at org.drools.template.parser.TemplateDataListener.<init>(TemplateDataListener.java:50)
at org.drools.template.ObjectDataCompiler.compile(ObjectDataCompiler.java:57)
at com.mycompany.mypackage.MyClass.init(MyClass.java:xxx)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at com.sun.ejb.containers.interceptors.BeanCallbackInterceptor.intercept(InterceptorManager.java:1035)
at com.sun.ejb.containers.interceptors.CallbackChainImpl.invokeNext(CallbackChainImpl.java:72)
at com.sun.ejb.containers.interceptors.CallbackInvocationContext.proceed(CallbackInvocationContext.java:205)
at org.jboss.weld.ejb.AbstractEJBRequestScopeActivationInterceptor.aroundInvoke(AbstractEJBRequestScopeActivationInterceptor.java:73)
at org.jboss.weld.ejb.SessionBeanInterceptor.aroundInvoke(SessionBeanInterceptor.java:52)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at com.sun.ejb.containers.interceptors.CallbackInterceptor.intercept(InterceptorManager.java:986)
at com.sun.ejb.containers.interceptors.CallbackChainImpl.invokeNext(CallbackChainImpl.java:72)
at com.sun.ejb.containers.interceptors.CallbackInvocationContext.proceed(CallbackInvocationContext.java:205)
at com.sun.ejb.containers.interceptors.SystemInterceptorProxy.doCall(SystemInterceptorProxy.java:163)
at com.sun.ejb.containers.interceptors.SystemInterceptorProxy.init(SystemInterceptorProxy.java:125)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at com.sun.ejb.containers.interceptors.CallbackInterceptor.intercept(InterceptorManager.java:986)
at com.sun.ejb.containers.interceptors.CallbackChainImpl.invokeNext(CallbackChainImpl.java:72)
at com.sun.ejb.containers.interceptors.InterceptorManager.intercept(InterceptorManager.java:412)
at com.sun.ejb.containers.interceptors.InterceptorManager.intercept(InterceptorManager.java:375)
at com.sun.ejb.containers.BaseContainer.intercept(BaseContainer.java:2014)
at com.sun.ejb.containers.AbstractSingletonContainer.createSingletonEJB(AbstractSingletonContainer.java:468)
at com.sun.ejb.containers.AbstractSingletonContainer.access$000(AbstractSingletonContainer.java:74)
at com.sun.ejb.containers.AbstractSingletonContainer$SingletonContextFactory.create(AbstractSingletonContainer.java:647)
at com.sun.ejb.containers.AbstractSingletonContainer.instantiateSingletonInstance(AbstractSingletonContainer.java:389)
at org.glassfish.ejb.startup.SingletonLifeCycleManager.initializeSingleton(SingletonLifeCycleManager.java:219)
at org.glassfish.ejb.startup.SingletonLifeCycleManager.initializeSingleton(SingletonLifeCycleManager.java:180)
at org.glassfish.ejb.startup.SingletonLifeCycleManager.doStartup(SingletonLifeCycleManager.java:158)
at org.glassfish.ejb.startup.EjbApplication.start(EjbApplication.java:166)
...
{noformat}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (WFLY-6746) HAL does not allow to manage different patching streams
by Bartosz Baranowski (JIRA)
Bartosz Baranowski created WFLY-6746:
----------------------------------------
Summary: HAL does not allow to manage different patching streams
Key: WFLY-6746
URL: https://issues.jboss.org/browse/WFLY-6746
Project: WildFly
Issue Type: Bug
Reporter: Bartosz Baranowski
Assignee: Jason Greene
Changes introduced to WFCORE and CLI/Patching allow different patching streams to be applied managed on EAP platform. This change has not been reflected in HAL. As is, it will allow to manage and apply patches for EAP main stream, however, patch from different stream can only be applied, not managed.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months