[JBoss JIRA] (AS7-6565) single jdbc driver deployed inside ear takes name of ear
by Stefano Maestri (JIRA)
[ https://issues.jboss.org/browse/AS7-6565?page=com.atlassian.jira.plugin.s... ]
Stefano Maestri commented on AS7-6565:
--------------------------------------
Last PR changes implement this driver-name this way:
1) in case the archive is a jar and contains only one driver driver-name==jarName (as was before)
2) in case the archive is not a jar and/or it cointains more than one driver driver-name==deploymentUnit.getName() + "_" + driverClassName + "_" + majorVersion +"_" + minorVersion
3) added info level logs saying "JBAS010417: Started Driver service with driver-name = postgresql-9.0-801.jdbc4.jar" or "JBAS010417: Started Driver service with driver-name = test.ear_org.postgresql.Driver_9_0" and logging also stop of those services for example: "JBAS010418: Stopped Driver service with driver-name = postgresql-9.0-801.jdbc4.jar" or "JBAS010418: Stopped Driver service with driver-name = h2"
it should guarantee backward compatibility for single driver jar deployment (the most used case), while is fixing the obscure naming in case of single driver deployed as part of an ear.
> single jdbc driver deployed inside ear takes name of ear
> --------------------------------------------------------
>
> Key: AS7-6565
> URL: https://issues.jboss.org/browse/AS7-6565
> Project: Application Server 7
> Issue Type: Feature Request
> Components: JCA
> Affects Versions: 7.1.1.Final, 8.0.0.Alpha1
> Reporter: Tom Eicher
> Assignee: Stefano Maestri
>
> We need to always give service name for jdbdriver as
> {code}
> deploymentUnit.getName() + "_" + driverClassName + "_" + majorVersion +"_" + minorVersion
> {code}
> even if thre is only one driver in the deployment unit. Current behavior is to give just deploymentUnit name in case of only one driver in. The changes makes more clear/readable driver names.
> Original description was:
> Including a JDBC driver, in this case PostgreSQL, in an ear like
> {code}
> myapp.ear:
> lib/postgresql-9.1-901.jdbc4.jar
> {code}
> does deploy the driver:
> {code}
> 23:37:28,118 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-1) JBAS010404: Deploying non-JDBC-compliant driver class org.postgresql.Driver (version 9.1)
> {code}
> however the service name is not {{postgresql_9_1_901_jdbc4_jar}} as expected,
> but it's {{myapp_ear}}.
> (Seen in admin console, and this is the only value accepted in my -ds.xml file.)
> 1. JDBC driver service should pick name of innermost jar, not of containing ear
> 2. driver name (as to be used in datasource definition) should be logged with the log message above.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 2 months
[JBoss JIRA] (AS7-6565) single jdbc driver deployed inside ear takes name of ear
by Stefano Maestri (JIRA)
[ https://issues.jboss.org/browse/AS7-6565?page=com.atlassian.jira.plugin.s... ]
Stefano Maestri updated AS7-6565:
---------------------------------
Git Pull Request: https://github.com/jbossas/jboss-as/pull/4111, https://github.com/jbossas/jboss-as/pull/4141 (was: https://github.com/jbossas/jboss-as/pull/4111)
> single jdbc driver deployed inside ear takes name of ear
> --------------------------------------------------------
>
> Key: AS7-6565
> URL: https://issues.jboss.org/browse/AS7-6565
> Project: Application Server 7
> Issue Type: Feature Request
> Components: JCA
> Affects Versions: 7.1.1.Final, 8.0.0.Alpha1
> Reporter: Tom Eicher
> Assignee: Stefano Maestri
>
> We need to always give service name for jdbdriver as
> {code}
> deploymentUnit.getName() + "_" + driverClassName + "_" + majorVersion +"_" + minorVersion
> {code}
> even if thre is only one driver in the deployment unit. Current behavior is to give just deploymentUnit name in case of only one driver in. The changes makes more clear/readable driver names.
> Original description was:
> Including a JDBC driver, in this case PostgreSQL, in an ear like
> {code}
> myapp.ear:
> lib/postgresql-9.1-901.jdbc4.jar
> {code}
> does deploy the driver:
> {code}
> 23:37:28,118 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-1) JBAS010404: Deploying non-JDBC-compliant driver class org.postgresql.Driver (version 9.1)
> {code}
> however the service name is not {{postgresql_9_1_901_jdbc4_jar}} as expected,
> but it's {{myapp_ear}}.
> (Seen in admin console, and this is the only value accepted in my -ds.xml file.)
> 1. JDBC driver service should pick name of innermost jar, not of containing ear
> 2. driver name (as to be used in datasource definition) should be logged with the log message above.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 2 months
[JBoss JIRA] (JGRP-653) Streaming API for large messages
by Andrea Carboni (JIRA)
[ https://issues.jboss.org/browse/JGRP-653?page=com.atlassian.jira.plugin.s... ]
Andrea Carboni commented on JGRP-653:
-------------------------------------
Having a streaming API would be very usefull. We are using jgroups as a better alternative respect to EBJs.
> Streaming API for large messages
> --------------------------------
>
> Key: JGRP-653
> URL: https://issues.jboss.org/browse/JGRP-653
> Project: JGroups
> Issue Type: Feature Request
> Reporter: Bela Ban
> Assignee: Bela Ban
> Fix For: 3.x
>
> Attachments: JGroupsInputStream.java, JGroupsOutputStream.java, StreamTest.java
>
>
> For large messages, to load the entire payload into memory might be bad because the payload might be bigger than the max memory available. It would be useful to have an API which allows for use of input and output streams, so that large payloads can be read iteratively by a user and streamed out to the cluster via the underlying channel breaking the data in the input stream into chunks, which are fed into the input stream on the receivers side.
> Issues: we have to have 1 input stream per sender on the receiver side, because a stream is always defined between 2 parties (sender, receiver). Maybe something like NIO, where we register interest in a stream, are notified of new streams ('accept()') and get notified when data on any of the stream is available, would be beneficial.
> Demo is attached
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 2 months
[JBoss JIRA] (DROOLS-59) CorrelationAwareProcessRuntime is not visible by classloader of drools-core
by Geoffrey De Smet (JIRA)
[ https://issues.jboss.org/browse/DROOLS-59?page=com.atlassian.jira.plugin.... ]
Geoffrey De Smet commented on DROOLS-59:
----------------------------------------
Check jbpm?
> CorrelationAwareProcessRuntime is not visible by classloader of drools-core
> ---------------------------------------------------------------------------
>
> Key: DROOLS-59
> URL: https://issues.jboss.org/browse/DROOLS-59
> Project: Drools
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Reporter: Charles Moulliard
> Assignee: Mark Proctor
>
> As this class CorrelationAwareProcessRuntime does not exist in the Drools project, I don't really understand why we get this exception
> {code}
> karaf@root> Exception in thread "SpringOsgiExtenderThread-2" org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'kbase1': Invocation of init method failed; nested exception is java.lang.NoClassDefFoundError: org/kie/process/CorrelationAwareProcessRuntime
> at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1422)
> at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:518)
> at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:455)
> at org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:293)
> at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:222)
> at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:290)
> at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:192)
> at org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons(DefaultListableBeanFactory.java:567)
> at org.springframework.context.support.AbstractApplicationContext.finishBeanFactoryInitialization(AbstractApplicationContext.java:895)
> at org.springframework.osgi.context.support.AbstractDelegatedExecutionApplicationContext.access$1600(AbstractDelegatedExecutionApplicationContext.java:69)
> at org.springframework.osgi.context.support.AbstractDelegatedExecutionApplicationContext$4.run(AbstractDelegatedExecutionApplicationContext.java:355)
> at org.springframework.osgi.util.internal.PrivilegedUtils.executeWithCustomTCCL(PrivilegedUtils.java:85)
> at org.springframework.osgi.context.support.AbstractDelegatedExecutionApplicationContext.completeRefresh(AbstractDelegatedExecutionApplicationContext.java:320)
> at org.springframework.osgi.extender.internal.dependencies.startup.DependencyWaiterApplicationContextExecutor$CompleteRefreshTask.run(DependencyWaiterApplicationContextExecutor.java:132)
> at java.lang.Thread.run(Thread.java:680)
> Caused by: java.lang.NoClassDefFoundError: org/kie/process/CorrelationAwareProcessRuntime
> at java.lang.ClassLoader.defineClass1(Native Method)
> at java.lang.ClassLoader.defineClassCond(ClassLoader.java:631)
> at java.lang.ClassLoader.defineClass(ClassLoader.java:615)
> at org.apache.felix.framework.BundleWiringImpl$BundleClassLoader.findClass(BundleWiringImpl.java:2128)
> at org.apache.felix.framework.BundleWiringImpl.findClassOrResourceByDelegation(BundleWiringImpl.java:1432)
> at org.apache.felix.framework.BundleWiringImpl.access$400(BundleWiringImpl.java:72)
> at org.apache.felix.framework.BundleWiringImpl$BundleClassLoader.loadClass(BundleWiringImpl.java:1843)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:247)
> at java.lang.ClassLoader.defineClass1(Native Method)
> at java.lang.ClassLoader.defineClassCond(ClassLoader.java:631)
> at java.lang.ClassLoader.defineClass(ClassLoader.java:615)
> at org.apache.felix.framework.BundleWiringImpl$BundleClassLoader.findClass(BundleWiringImpl.java:2128)
> at org.apache.felix.framework.BundleWiringImpl.findClassOrResourceByDelegation(BundleWiringImpl.java:1432)
> at org.apache.felix.framework.BundleWiringImpl.access$400(BundleWiringImpl.java:72)
> at org.apache.felix.framework.BundleWiringImpl$BundleClassLoader.loadClass(BundleWiringImpl.java:1843)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:247)
> at org.drools.impl.KnowledgeBaseFactoryServiceImpl.newKnowledgeBase(KnowledgeBaseFactoryServiceImpl.java:57)
> at org.drools.container.spring.beans.KnowledgeBaseBeanFactory.afterPropertiesSet(KnowledgeBaseBeanFactory.java:97)
> at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.invokeInitMethods(AbstractAutowireCapableBeanFactory.java:1479)
> at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1419)
> ... 14 more
> Caused by: java.lang.ClassNotFoundException: org.kie.process.CorrelationAwareProcessRuntime not found by org.drools.karaf.drools-component [119]
> at org.apache.felix.framework.BundleWiringImpl.findClassOrResourceByDelegation(BundleWiringImpl.java:1460)
> at org.apache.felix.framework.BundleWiringImpl.access$400(BundleWiringImpl.java:72)
> at org.apache.felix.framework.BundleWiringImpl$BundleClassLoader.loadClass(BundleWiringImpl.java:1843)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:247)
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 2 months
[JBoss JIRA] (DROOLS-57) Split packages: OSGi packaging issue/conflict with Kie API & Kie Internal
by Geoffrey De Smet (JIRA)
[ https://issues.jboss.org/browse/DROOLS-57?page=com.atlassian.jira.plugin.... ]
Geoffrey De Smet updated DROOLS-57:
-----------------------------------
Summary: Split packages: OSGi packaging issue/conflict with Kie API & Kie Internal (was: Packaging issue/conflict with Kie API & Kie Internal)
> Split packages: OSGi packaging issue/conflict with Kie API & Kie Internal
> -------------------------------------------------------------------------
>
> Key: DROOLS-57
> URL: https://issues.jboss.org/browse/DROOLS-57
> Project: Drools
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Reporter: Charles Moulliard
> Assignee: Mark Proctor
>
> Due to overlap of packages between module kie-api & kie-internal, some classes of kie-internal are not found by kie-api
> example :
> Caused by: java.lang.ClassNotFoundException: org.kie.KieBaseConfiguration not found by org.kie.api [88] = KIE API
> The class org.kie.KieBaseConfiguration should be exported by the bundle kie-internal and imported by kie-api on OSGI platform and this is not the case as both bundles import/export same package org.kie
> {code}
> Bundle 88 = kie api & bundle 89 = kie internal
> karaf@root> packages:exports 88
> ID Packages
> 88 org.kie.event.rule; version=6.0.0.SNAPSHOT
> 88 org.kie.command; version=6.0.0.SNAPSHOT
> 88 org.kie.event.kiebase; version=6.0.0.SNAPSHOT
> 88 org.kie.definition; version=6.0.0.SNAPSHOT
> 88 org.kie.definition.process; version=6.0.0.SNAPSHOT
> 88 org.kie.runtime.rule; version=6.0.0.SNAPSHOT
> 88 org.kie.event.process; version=6.0.0.SNAPSHOT
> 88 org.kie.conf; version=6.0.0.SNAPSHOT
> 88 org.kie.runtime.help; version=6.0.0.SNAPSHOT
> 88 org.kie.runtime.conf; version=6.0.0.SNAPSHOT
> 88 org.kie.management; version=6.0.0.SNAPSHOT
> 88 org.kie.definition.type; version=6.0.0.SNAPSHOT
> 88 org.kie.definition.rule; version=6.0.0.SNAPSHOT
> 88 org.kie.io; version=6.0.0.SNAPSHOT
> 88 org.kie.marshalling; version=6.0.0.SNAPSHOT
> 88 org.kie.builder.model; version=6.0.0.SNAPSHOT
> 88 org.kie.time; version=6.0.0.SNAPSHOT
> 88 org.kie; version=6.0.0.SNAPSHOT
> 88 org.kie.runtime; version=6.0.0.SNAPSHOT
> 88 org.kie.runtime.process; version=6.0.0.SNAPSHOT
> 88 org.kie.logger; version=6.0.0.SNAPSHOT
> 88 org.kie.builder; version=6.0.0.SNAPSHOT
> 88 org.kie.concurrent; version=6.0.0.SNAPSHOT
> 88 org.kie.cdi; version=6.0.0.SNAPSHOT
> 88 org.kie.persistence.jpa; version=6.0.0.SNAPSHOT
> 88 org.kie.osgi.api; version=6.0.0.SNAPSHOT
> 88 org.kie.event; version=6.0.0.SNAPSHOT
> karaf@root> packages:exports 89
> ID Packages
> 89 org.kie.event.rule; version=6.0.0.SNAPSHOT
> 89 org.kie.command; version=6.0.0.SNAPSHOT
> 89 org.kie.internal.utils; version=6.0.0.SNAPSHOT
> 89 org.kie.runtime.helper; version=6.0.0.SNAPSHOT
> 89 org.kie.builder.conf; version=6.0.0.SNAPSHOT
> 89 org.kie.fluent; version=6.0.0.SNAPSHOT
> 89 org.kie.definition; version=6.0.0.SNAPSHOT
> 89 org.kie.conf; version=6.0.0.SNAPSHOT
> 89 org.kie.builder.help; version=6.0.0.SNAPSHOT
> 89 org.kie.io; version=6.0.0.SNAPSHOT
> 89 org.kie.event.io; version=6.0.0.SNAPSHOT
> 89 org.kie.marshalling; version=6.0.0.SNAPSHOT
> 89 org.kie.fluent.test; version=6.0.0.SNAPSHOT
> 89 org.kie.agent.conf; version=6.0.0.SNAPSHOT
> 89 org.kie; version=6.0.0.SNAPSHOT
> 89 org.kie.runtime; version=6.0.0.SNAPSHOT
> 89 org.kie.simulation; version=6.0.0.SNAPSHOT
> 89 org.kie.event.knowledgeagent; version=6.0.0.SNAPSHOT
> 89 org.kie.logger; version=6.0.0.SNAPSHOT
> 89 org.kie.builder; version=6.0.0.SNAPSHOT
> 89 org.kie.concurrent; version=6.0.0.SNAPSHOT
> 89 org.kie.persistence.jpa; version=6.0.0.SNAPSHOT
> 89 org.kie.agent; version=6.0.0.SNAPSHOT
> 89 org.kie.event; version=6.0.0.SNAPSHOT
> 89 org.kie.task.service; version=6.0.0.SNAPSHOT
> karaf@root> packages:imports 89
> System Bundle (0): javax.xml.bind; version=2.2.1
> OPS4J Pax Logging - API (4): org.slf4j; version=1.7.1
> OPS4J Pax Logging - API (4): org.slf4j; version=1.6.6
> OPS4J Pax Logging - API (4): org.slf4j; version=1.5.11
> OPS4J Pax Logging - API (4): org.slf4j; version=1.4.3
> Apache ServiceMix :: Bundles :: xstream (57): com.thoughtworks.xstream; version=1.4.3
> KIE API (88): org.kie.event.rule; version=6.0.0.SNAPSHOT
> KIE API (88): org.kie.command; version=6.0.0.SNAPSHOT
> KIE API (88): org.kie.event.kiebase; version=6.0.0.SNAPSHOT
> KIE API (88): org.kie.definition; version=6.0.0.SNAPSHOT
> KIE API (88): org.kie.definition.process; version=6.0.0.SNAPSHOT
> KIE API (88): org.kie.runtime.rule; version=6.0.0.SNAPSHOT
> KIE API (88): org.kie.event.process; version=6.0.0.SNAPSHOT
> KIE API (88): org.kie.conf; version=6.0.0.SNAPSHOT
> KIE API (88): org.kie.runtime.help; version=6.0.0.SNAPSHOT
> KIE API (88): org.kie.runtime.conf; version=6.0.0.SNAPSHOT
> KIE API (88): org.kie.management; version=6.0.0.SNAPSHOT
> KIE API (88): org.kie.definition.type; version=6.0.0.SNAPSHOT
> KIE API (88): org.kie.definition.rule; version=6.0.0.SNAPSHOT
> KIE API (88): org.kie.io; version=6.0.0.SNAPSHOT
> KIE API (88): org.kie.marshalling; version=6.0.0.SNAPSHOT
> KIE API (88): org.kie.builder.model; version=6.0.0.SNAPSHOT
> KIE API (88): org.kie.time; version=6.0.0.SNAPSHOT
> KIE API (88): org.kie; version=6.0.0.SNAPSHOT
> KIE API (88): org.kie.runtime; version=6.0.0.SNAPSHOT
> KIE API (88): org.kie.runtime.process; version=6.0.0.SNAPSHOT
> KIE API (88): org.kie.logger; version=6.0.0.SNAPSHOT
> KIE API (88): org.kie.builder; version=6.0.0.SNAPSHOT
> KIE API (88): org.kie.concurrent; version=6.0.0.SNAPSHOT
> KIE API (88): org.kie.cdi; version=6.0.0.SNAPSHOT
> KIE API (88): org.kie.persistence.jpa; version=6.0.0.SNAPSHOT
> KIE API (88): org.kie.osgi.api; version=6.0.0.SNAPSHOT
> KIE API (88): org.kie.event; version=6.0.0.SNAPSHOT
> camel-core (229): org.apache.camel.spi; version=2.10.3
> camel-core (229): org.apache.camel; version=2.10.3
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 2 months
[JBoss JIRA] (DROOLS-57) Packaging issue/conflict with Kie API & Kie Internal
by Mario Fusco (JIRA)
[ https://issues.jboss.org/browse/DROOLS-57?page=com.atlassian.jira.plugin.... ]
Mario Fusco updated DROOLS-57:
------------------------------
Issue Type: Bug (was: Feature Request)
> Packaging issue/conflict with Kie API & Kie Internal
> ----------------------------------------------------
>
> Key: DROOLS-57
> URL: https://issues.jboss.org/browse/DROOLS-57
> Project: Drools
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Reporter: Charles Moulliard
> Assignee: Mark Proctor
>
> Due to overlap of packages between module kie-api & kie-internal, some classes of kie-internal are not found by kie-api
> example :
> Caused by: java.lang.ClassNotFoundException: org.kie.KieBaseConfiguration not found by org.kie.api [88] = KIE API
> The class org.kie.KieBaseConfiguration should be exported by the bundle kie-internal and imported by kie-api on OSGI platform and this is not the case as both bundles import/export same package org.kie
> {code}
> Bundle 88 = kie api & bundle 89 = kie internal
> karaf@root> packages:exports 88
> ID Packages
> 88 org.kie.event.rule; version=6.0.0.SNAPSHOT
> 88 org.kie.command; version=6.0.0.SNAPSHOT
> 88 org.kie.event.kiebase; version=6.0.0.SNAPSHOT
> 88 org.kie.definition; version=6.0.0.SNAPSHOT
> 88 org.kie.definition.process; version=6.0.0.SNAPSHOT
> 88 org.kie.runtime.rule; version=6.0.0.SNAPSHOT
> 88 org.kie.event.process; version=6.0.0.SNAPSHOT
> 88 org.kie.conf; version=6.0.0.SNAPSHOT
> 88 org.kie.runtime.help; version=6.0.0.SNAPSHOT
> 88 org.kie.runtime.conf; version=6.0.0.SNAPSHOT
> 88 org.kie.management; version=6.0.0.SNAPSHOT
> 88 org.kie.definition.type; version=6.0.0.SNAPSHOT
> 88 org.kie.definition.rule; version=6.0.0.SNAPSHOT
> 88 org.kie.io; version=6.0.0.SNAPSHOT
> 88 org.kie.marshalling; version=6.0.0.SNAPSHOT
> 88 org.kie.builder.model; version=6.0.0.SNAPSHOT
> 88 org.kie.time; version=6.0.0.SNAPSHOT
> 88 org.kie; version=6.0.0.SNAPSHOT
> 88 org.kie.runtime; version=6.0.0.SNAPSHOT
> 88 org.kie.runtime.process; version=6.0.0.SNAPSHOT
> 88 org.kie.logger; version=6.0.0.SNAPSHOT
> 88 org.kie.builder; version=6.0.0.SNAPSHOT
> 88 org.kie.concurrent; version=6.0.0.SNAPSHOT
> 88 org.kie.cdi; version=6.0.0.SNAPSHOT
> 88 org.kie.persistence.jpa; version=6.0.0.SNAPSHOT
> 88 org.kie.osgi.api; version=6.0.0.SNAPSHOT
> 88 org.kie.event; version=6.0.0.SNAPSHOT
> karaf@root> packages:exports 89
> ID Packages
> 89 org.kie.event.rule; version=6.0.0.SNAPSHOT
> 89 org.kie.command; version=6.0.0.SNAPSHOT
> 89 org.kie.internal.utils; version=6.0.0.SNAPSHOT
> 89 org.kie.runtime.helper; version=6.0.0.SNAPSHOT
> 89 org.kie.builder.conf; version=6.0.0.SNAPSHOT
> 89 org.kie.fluent; version=6.0.0.SNAPSHOT
> 89 org.kie.definition; version=6.0.0.SNAPSHOT
> 89 org.kie.conf; version=6.0.0.SNAPSHOT
> 89 org.kie.builder.help; version=6.0.0.SNAPSHOT
> 89 org.kie.io; version=6.0.0.SNAPSHOT
> 89 org.kie.event.io; version=6.0.0.SNAPSHOT
> 89 org.kie.marshalling; version=6.0.0.SNAPSHOT
> 89 org.kie.fluent.test; version=6.0.0.SNAPSHOT
> 89 org.kie.agent.conf; version=6.0.0.SNAPSHOT
> 89 org.kie; version=6.0.0.SNAPSHOT
> 89 org.kie.runtime; version=6.0.0.SNAPSHOT
> 89 org.kie.simulation; version=6.0.0.SNAPSHOT
> 89 org.kie.event.knowledgeagent; version=6.0.0.SNAPSHOT
> 89 org.kie.logger; version=6.0.0.SNAPSHOT
> 89 org.kie.builder; version=6.0.0.SNAPSHOT
> 89 org.kie.concurrent; version=6.0.0.SNAPSHOT
> 89 org.kie.persistence.jpa; version=6.0.0.SNAPSHOT
> 89 org.kie.agent; version=6.0.0.SNAPSHOT
> 89 org.kie.event; version=6.0.0.SNAPSHOT
> 89 org.kie.task.service; version=6.0.0.SNAPSHOT
> karaf@root> packages:imports 89
> System Bundle (0): javax.xml.bind; version=2.2.1
> OPS4J Pax Logging - API (4): org.slf4j; version=1.7.1
> OPS4J Pax Logging - API (4): org.slf4j; version=1.6.6
> OPS4J Pax Logging - API (4): org.slf4j; version=1.5.11
> OPS4J Pax Logging - API (4): org.slf4j; version=1.4.3
> Apache ServiceMix :: Bundles :: xstream (57): com.thoughtworks.xstream; version=1.4.3
> KIE API (88): org.kie.event.rule; version=6.0.0.SNAPSHOT
> KIE API (88): org.kie.command; version=6.0.0.SNAPSHOT
> KIE API (88): org.kie.event.kiebase; version=6.0.0.SNAPSHOT
> KIE API (88): org.kie.definition; version=6.0.0.SNAPSHOT
> KIE API (88): org.kie.definition.process; version=6.0.0.SNAPSHOT
> KIE API (88): org.kie.runtime.rule; version=6.0.0.SNAPSHOT
> KIE API (88): org.kie.event.process; version=6.0.0.SNAPSHOT
> KIE API (88): org.kie.conf; version=6.0.0.SNAPSHOT
> KIE API (88): org.kie.runtime.help; version=6.0.0.SNAPSHOT
> KIE API (88): org.kie.runtime.conf; version=6.0.0.SNAPSHOT
> KIE API (88): org.kie.management; version=6.0.0.SNAPSHOT
> KIE API (88): org.kie.definition.type; version=6.0.0.SNAPSHOT
> KIE API (88): org.kie.definition.rule; version=6.0.0.SNAPSHOT
> KIE API (88): org.kie.io; version=6.0.0.SNAPSHOT
> KIE API (88): org.kie.marshalling; version=6.0.0.SNAPSHOT
> KIE API (88): org.kie.builder.model; version=6.0.0.SNAPSHOT
> KIE API (88): org.kie.time; version=6.0.0.SNAPSHOT
> KIE API (88): org.kie; version=6.0.0.SNAPSHOT
> KIE API (88): org.kie.runtime; version=6.0.0.SNAPSHOT
> KIE API (88): org.kie.runtime.process; version=6.0.0.SNAPSHOT
> KIE API (88): org.kie.logger; version=6.0.0.SNAPSHOT
> KIE API (88): org.kie.builder; version=6.0.0.SNAPSHOT
> KIE API (88): org.kie.concurrent; version=6.0.0.SNAPSHOT
> KIE API (88): org.kie.cdi; version=6.0.0.SNAPSHOT
> KIE API (88): org.kie.persistence.jpa; version=6.0.0.SNAPSHOT
> KIE API (88): org.kie.osgi.api; version=6.0.0.SNAPSHOT
> KIE API (88): org.kie.event; version=6.0.0.SNAPSHOT
> camel-core (229): org.apache.camel.spi; version=2.10.3
> camel-core (229): org.apache.camel; version=2.10.3
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 2 months
[JBoss JIRA] (AS7-4331) Management operations for accessing transaction logs should be exposed in the web console
by Heiko Braun (JIRA)
[ https://issues.jboss.org/browse/AS7-4331?page=com.atlassian.jira.plugin.s... ]
Heiko Braun updated AS7-4331:
-----------------------------
Attachment: tx-log.txt
Example log store output
> Management operations for accessing transaction logs should be exposed in the web console
> -----------------------------------------------------------------------------------------
>
> Key: AS7-4331
> URL: https://issues.jboss.org/browse/AS7-4331
> Project: Application Server 7
> Issue Type: Bug
> Components: Console
> Affects Versions: 7.1.1.Final
> Reporter: Michael Musgrove
> Assignee: Heiko Braun
> Fix For: No Release
>
> Attachments: tx-log.txt
>
>
> Task AS7-925 provides CLI management operations for accessing transaction logs.
> We need the same information to be made available in the web console.
> The operations are part of the log store sub model:
> org.jboss.as.txn.subsystem.LogStoreAddHandler
> We also need to expose the attribute for switching our log store implementation:
> TransactionSubsystemRootResourceDefinition.USEHORNETQSTORE
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 2 months
[JBoss JIRA] (DROOLS-59) CorrelationAwareProcessRuntime is not visible by classloader of drools-core
by Charles Moulliard (JIRA)
Charles Moulliard created DROOLS-59:
---------------------------------------
Summary: CorrelationAwareProcessRuntime is not visible by classloader of drools-core
Key: DROOLS-59
URL: https://issues.jboss.org/browse/DROOLS-59
Project: Drools
Issue Type: Bug
Security Level: Public (Everyone can see)
Reporter: Charles Moulliard
Assignee: Mark Proctor
As this class CorrelationAwareProcessRuntime does not exist in the Drools project, I don't really understand why we get this exeption
{code}
karaf@root> Exception in thread "SpringOsgiExtenderThread-2" org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'kbase1': Invocation of init method failed; nested exception is java.lang.NoClassDefFoundError: org/kie/process/CorrelationAwareProcessRuntime
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1422)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:518)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:455)
at org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:293)
at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:222)
at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:290)
at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:192)
at org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons(DefaultListableBeanFactory.java:567)
at org.springframework.context.support.AbstractApplicationContext.finishBeanFactoryInitialization(AbstractApplicationContext.java:895)
at org.springframework.osgi.context.support.AbstractDelegatedExecutionApplicationContext.access$1600(AbstractDelegatedExecutionApplicationContext.java:69)
at org.springframework.osgi.context.support.AbstractDelegatedExecutionApplicationContext$4.run(AbstractDelegatedExecutionApplicationContext.java:355)
at org.springframework.osgi.util.internal.PrivilegedUtils.executeWithCustomTCCL(PrivilegedUtils.java:85)
at org.springframework.osgi.context.support.AbstractDelegatedExecutionApplicationContext.completeRefresh(AbstractDelegatedExecutionApplicationContext.java:320)
at org.springframework.osgi.extender.internal.dependencies.startup.DependencyWaiterApplicationContextExecutor$CompleteRefreshTask.run(DependencyWaiterApplicationContextExecutor.java:132)
at java.lang.Thread.run(Thread.java:680)
Caused by: java.lang.NoClassDefFoundError: org/kie/process/CorrelationAwareProcessRuntime
at java.lang.ClassLoader.defineClass1(Native Method)
at java.lang.ClassLoader.defineClassCond(ClassLoader.java:631)
at java.lang.ClassLoader.defineClass(ClassLoader.java:615)
at org.apache.felix.framework.BundleWiringImpl$BundleClassLoader.findClass(BundleWiringImpl.java:2128)
at org.apache.felix.framework.BundleWiringImpl.findClassOrResourceByDelegation(BundleWiringImpl.java:1432)
at org.apache.felix.framework.BundleWiringImpl.access$400(BundleWiringImpl.java:72)
at org.apache.felix.framework.BundleWiringImpl$BundleClassLoader.loadClass(BundleWiringImpl.java:1843)
at java.lang.ClassLoader.loadClass(ClassLoader.java:247)
at java.lang.ClassLoader.defineClass1(Native Method)
at java.lang.ClassLoader.defineClassCond(ClassLoader.java:631)
at java.lang.ClassLoader.defineClass(ClassLoader.java:615)
at org.apache.felix.framework.BundleWiringImpl$BundleClassLoader.findClass(BundleWiringImpl.java:2128)
at org.apache.felix.framework.BundleWiringImpl.findClassOrResourceByDelegation(BundleWiringImpl.java:1432)
at org.apache.felix.framework.BundleWiringImpl.access$400(BundleWiringImpl.java:72)
at org.apache.felix.framework.BundleWiringImpl$BundleClassLoader.loadClass(BundleWiringImpl.java:1843)
at java.lang.ClassLoader.loadClass(ClassLoader.java:247)
at org.drools.impl.KnowledgeBaseFactoryServiceImpl.newKnowledgeBase(KnowledgeBaseFactoryServiceImpl.java:57)
at org.drools.container.spring.beans.KnowledgeBaseBeanFactory.afterPropertiesSet(KnowledgeBaseBeanFactory.java:97)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.invokeInitMethods(AbstractAutowireCapableBeanFactory.java:1479)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1419)
... 14 more
Caused by: java.lang.ClassNotFoundException: org.kie.process.CorrelationAwareProcessRuntime not found by org.drools.karaf.drools-component [119]
at org.apache.felix.framework.BundleWiringImpl.findClassOrResourceByDelegation(BundleWiringImpl.java:1460)
at org.apache.felix.framework.BundleWiringImpl.access$400(BundleWiringImpl.java:72)
at org.apache.felix.framework.BundleWiringImpl$BundleClassLoader.loadClass(BundleWiringImpl.java:1843)
at java.lang.ClassLoader.loadClass(ClassLoader.java:247)
{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 2 months