[JBoss JIRA] (WFLY-235) "Problems un-registering MBeans: CacheException: Failure while unregistering mbeans" on server shutdown
by Paul Ferraro (JIRA)
[ https://issues.jboss.org/browse/WFLY-235?page=com.atlassian.jira.plugin.s... ]
Paul Ferraro resolved WFLY-235.
-------------------------------
Resolution: Out of Date
This is no longer an issue in Wildfly.
> "Problems un-registering MBeans: CacheException: Failure while unregistering mbeans" on server shutdown
> -------------------------------------------------------------------------------------------------------
>
> Key: WFLY-235
> URL: https://issues.jboss.org/browse/WFLY-235
> Project: WildFly
> Issue Type: Enhancement
> Components: Clustering
> Reporter: Radoslav Husar
> Assignee: Paul Ferraro
> Fix For: 8.0.0.Beta1
>
>
> Just saw this when i was closely checking logs from clustering testsuite.
> Affected: master 8a6aac3c8eb6bc94b7eddfa4d090c9ac05c7e37b
> {code}
> 15:09:34,380 INFO [org.apache.catalina.core] (MSC service thread 1-6) JBWEB001079: Container org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/] has not been started
> 15:09:34,381 INFO [org.apache.coyote.http11] (MSC service thread 1-1) JBWEB003075: Coyote HTTP/1.1 pausing on: http-/127.0.0.1:8180
> 15:09:34,381 INFO [org.apache.coyote.http11] (MSC service thread 1-1) JBWEB003077: Coyote HTTP/1.1 stopping on : http-/127.0.0.1:8180
> 15:09:34,385 INFO [org.jboss.web] (ServerService Thread Pool -- 55) JBAS018224: Unregister web context: /stateful
> 15:09:34,397 INFO [org.infinispan.eviction.PassivationManagerImpl] (ServerService Thread Pool -- 6) ISPN000029: Passivating all entries to disk
> 15:09:34,398 INFO [org.infinispan.eviction.PassivationManagerImpl] (ServerService Thread Pool -- 6) ISPN000030: Passivated 0 entries in 0 milliseconds
> 15:09:34,403 INFO [org.infinispan.eviction.PassivationManagerImpl] (ServerService Thread Pool -- 54) ISPN000029: Passivating all entries to disk
> 15:09:34,404 INFO [org.infinispan.eviction.PassivationManagerImpl] (ServerService Thread Pool -- 54) ISPN000030: Passivated 0 entries in 0 milliseconds
> 15:09:34,407 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 6) JBAS010282: Stopped org.jboss.as.test.clustering.cluster.ejb3.xpc.bean.StatefulBean cache from ejb container
> 15:09:34,407 INFO [org.apache.coyote.ajp] (MSC service thread 1-8) JBWEB003048: Pausing Coyote AJP/1.3 on ajp-/127.0.0.1:8109
> 15:09:34,408 INFO [org.apache.coyote.ajp] (MSC service thread 1-8) JBWEB003051: Stopping Coyote AJP/1.3 on ajp-/127.0.0.1:8109
> 15:09:34,411 INFO [org.infinispan.eviction.PassivationManagerImpl] (MSC service thread 1-2) ISPN000029: Passivating all entries to disk
> 15:09:34,411 INFO [org.infinispan.eviction.PassivationManagerImpl] (MSC service thread 1-2) ISPN000030: Passivated 0 entries in 0 milliseconds
> 15:09:34,413 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 54) JBAS010282: Stopped org.jboss.as.test.clustering.cluster.ejb3.xpc.bean.SecondBean cache from ejb container
> 15:09:34,419 INFO [org.jboss.as.clustering.infinispan] (MSC service thread 1-2) JBAS010282: Stopped default-host/stateful cache from web container
> 15:09:34,437 INFO [org.jboss.as.jpa] (ServerService Thread Pool -- 54) JBAS011403: Stopping Persistence Unit Service 'stateful.war#mypc'
> 15:09:34,440 INFO [org.infinispan.eviction.PassivationManagerImpl] (MSC service thread 1-3) ISPN000029: Passivating all entries to disk
> 15:09:34,440 INFO [org.infinispan.eviction.PassivationManagerImpl] (MSC service thread 1-3) ISPN000030: Passivated 0 entries in 0 milliseconds
> 15:09:34,445 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 54) JBAS010282: Stopped stateful.war#mypc.org.jboss.as.test.clustering.cluster.ejb3.xpc.bean.Employee cache from hibernate container
> 15:09:34,449 INFO [org.jboss.as.clustering.infinispan] (MSC service thread 1-3) JBAS010282: Stopped repl cache from web container
> 15:09:34,451 INFO [org.infinispan.eviction.PassivationManagerImpl] (MSC service thread 1-8) ISPN000029: Passivating all entries to disk
> 15:09:34,451 INFO [org.infinispan.eviction.PassivationManagerImpl] (MSC service thread 1-8) ISPN000030: Passivated 0 entries in 0 milliseconds
> 15:09:34,452 INFO [org.jboss.as.clustering.infinispan] (MSC service thread 1-1) JBAS010282: Stopped remote-connector-client-mappings cache from ejb container
> 15:09:34,459 INFO [org.infinispan.jmx.CacheJmxRegistration] (ServerService Thread Pool -- 54) ISPN000031: MBeans were successfully registered to the platform MBean server.
> 15:09:34,460 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (MSC service thread 1-3) ISPN000080: Disconnecting and closing JGroups Channel
> 15:09:34,460 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 54) JBAS010281: Started local-query cache from hibernate container
> 15:09:34,461 INFO [org.hibernate.tool.hbm2ddl.SchemaExport] (ServerService Thread Pool -- 54) HHH000227: Running hbm2ddl schema export
> 15:09:34,457 WARN [org.infinispan.jmx.CacheJmxRegistration] (MSC service thread 1-8) ISPN000032: Problems un-registering MBeans: org.infinispan.CacheException: Failure while unregistering mbeans
> at org.infinispan.jmx.ComponentsJmxRegistration.unregisterMBeans(ComponentsJmxRegistration.java:105)
> at org.infinispan.jmx.AbstractJmxRegistration.unregisterMBeans(AbstractJmxRegistration.java:70)
> at org.infinispan.jmx.CacheJmxRegistration.stop(CacheJmxRegistration.java:107)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [rt.jar:1.7.0_17]
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) [rt.jar:1.7.0_17]
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.7.0_17]
> at java.lang.reflect.Method.invoke(Method.java:601) [rt.jar:1.7.0_17]
> at org.infinispan.util.ReflectionUtil.invokeAccessibly(ReflectionUtil.java:203)
> at org.infinispan.factories.AbstractComponentRegistry$PrioritizedMethod.invoke(AbstractComponentRegistry.java:886)
> at org.infinispan.factories.AbstractComponentRegistry.internalStop(AbstractComponentRegistry.java:693)
> at org.infinispan.factories.AbstractComponentRegistry.stop(AbstractComponentRegistry.java:571)
> at org.infinispan.factories.ComponentRegistry.stop(ComponentRegistry.java:242)
> at org.infinispan.CacheImpl.stop(CacheImpl.java:604)
> at org.infinispan.CacheImpl.stop(CacheImpl.java:599)
> at org.infinispan.AbstractDelegatingCache.stop(AbstractDelegatingCache.java:348)
> at org.jboss.as.clustering.infinispan.subsystem.CacheService.stop(CacheService.java:96)
> at org.jboss.as.clustering.msc.AsynchronousService.stop(AsynchronousService.java:114) [jboss-as-clustering-common-8.0.0.Alpha1-SNAPSHOT.jar:8.0.0.Alpha1-SNAPSHOT]
> at org.jboss.msc.service.ServiceControllerImpl$StopTask.stopService(ServiceControllerImpl.java:2080) [jboss-msc-1.1.1.Final.jar:1.1.1.Final]
> at org.jboss.msc.service.ServiceControllerImpl$StopTask.run(ServiceControllerImpl.java:2041) [jboss-msc-1.1.1.Final.jar:1.1.1.Final]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_17]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_17]
> at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_17]
> Caused by: javax.management.InstanceNotFoundException: jboss.infinispan:type=Cache,name="repl(repl_sync)",manager="ejb",component=StateTransferManager
> at org.jboss.as.jmx.PluggableMBeanServerImpl.findDelegate(PluggableMBeanServerImpl.java:94)
> at org.jboss.as.jmx.PluggableMBeanServerImpl.unregisterMBean(PluggableMBeanServerImpl.java:360)
> at org.infinispan.jmx.JmxUtil.unregisterMBean(JmxUtil.java:112)
> at org.infinispan.jmx.ComponentsJmxRegistration.unregisterMBeans(ComponentsJmxRegistration.java:101)
> ... 21 more
> {code}
> Same as https://issues.jboss.org/browse/AS7-4247
--
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
12 years, 10 months
[JBoss JIRA] (AS7-4265) cli command to add/remove AS modules
by Manoj Agarwal (JIRA)
[ https://issues.jboss.org/browse/AS7-4265?page=com.atlassian.jira.plugin.s... ]
Manoj Agarwal commented on AS7-4265:
------------------------------------
Do we have provision to edit an existing module ? For example let's say if i already have a module in place and if i want to add one module dependency to it, can i do so ?
> cli command to add/remove AS modules
> ------------------------------------
>
> Key: AS7-4265
> URL: https://issues.jboss.org/browse/AS7-4265
> Project: Application Server 7
> Issue Type: Task
> Components: CLI
> Reporter: Alexey Loubyansky
> Assignee: Alexey Loubyansky
> Fix For: 7.1.2.Final (EAP)
>
>
> I think it'd be useful to have a command to add modules to the AS which given the jars, dependencies, etc would generate the structure in the modules dir, copy the jars and generate the xml.
--
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
12 years, 10 months
[JBoss JIRA] (WFLY-1873) mod_cluster ISE on shutdown
by Radoslav Husar (JIRA)
[ https://issues.jboss.org/browse/WFLY-1873?page=com.atlassian.jira.plugin.... ]
Radoslav Husar commented on WFLY-1873:
--------------------------------------
Great, thanks for the heads up. I just added it when I saw it locally.
The main problem is that when the notification api gives us control on application undeploy, the app is already undeployed and we cannot reconstruct the UndertowContext.
> mod_cluster ISE on shutdown
> ---------------------------
>
> Key: WFLY-1873
> URL: https://issues.jboss.org/browse/WFLY-1873
> Project: WildFly
> Issue Type: Bug
> Components: Clustering
> Affects Versions: 8.0.0.Alpha4
> Reporter: Radoslav Husar
> Assignee: Radoslav Husar
> Fix For: 8.0.0.Beta1
>
>
> 16:45:28,305 ERROR [org.jboss.modcluster.mcmp.impl.DefaultMCMPHandler] (MSC service thread 1-2) Error [MEM: MEM: Can't read node: {4}] sending command DISABLE-APP to proxy localhost/127.0.0.1:6666, configuration will be reset
> 16:45:28,315 INFO [org.wildfly.extension.undertow] (MSC service thread 1-8) JBAS017521: Undertow AJP listener ajp suspending
> 16:45:28,319 INFO [org.wildfly.extension.undertow] (MSC service thread 1-8) JBAS017520: Undertow AJP listener ajp stopped, was bound to /127.0.0.1:8009
> 16:45:28,336 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-4) JBAS010418: Stopped Driver service with driver-name = h2
> 16:45:28,344 INFO [org.wildfly.extension.undertow] (MSC service thread 1-8) JBAS017521: Undertow HTTP listener default suspending
> 16:45:28,349 INFO [org.wildfly.extension.undertow] (MSC service thread 1-8) JBAS017520: Undertow HTTP listener default stopped, was bound to /127.0.0.1:8080
> 16:45:38,307 WARN [org.jboss.modcluster.ModClusterService] (MSC service thread 1-2) Failed to drain pending requests from context [org.wildfly.mod_cluster.undertow.UndertowContext@1906d941] within specified timeout: 10 seconds
> 16:45:38,308 WARN [org.jboss.msc.service.fail] (MSC service thread 1-2) MSC000004: Failure during stop of service jboss.undertow.deployment.default-host./clusterbench-ee6-web: java.lang.IllegalStateException
> at org.jboss.msc.value.InjectedValue.getValue(InjectedValue.java:47) [jboss-msc-1.2.0.Beta2.jar:1.2.0.Beta2]
> at org.wildfly.mod_cluster.undertow.UndertowEventHandlerAdapter.onDeploymentStop(UndertowEventHandlerAdapter.java:137)
> at org.wildfly.extension.undertow.Host$2.invoke(Host.java:138)
> at org.wildfly.extension.undertow.UndertowService.fireEvent(UndertowService.java:168)
> at org.wildfly.extension.undertow.Host.unregisterDeployment(Host.java:135)
> at org.wildfly.extension.undertow.deployment.UndertowDeploymentService.stopContext(UndertowDeploymentService.java:104)
> at org.wildfly.extension.undertow.deployment.UndertowDeploymentService.stop(UndertowDeploymentService.java:94)
> at org.jboss.msc.service.ServiceControllerImpl$StopTask.stopService(ServiceControllerImpl.java:2052) [jboss-msc-1.2.0.Beta2.jar:1.2.0.Beta2]
> at org.jboss.msc.service.ServiceControllerImpl$StopTask.run(ServiceControllerImpl.java:2013) [jboss-msc-1.2.0.Beta2.jar:1.2.0.Beta2]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_25]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_25]
> at java.lang.Thread.run(Thread.java:724) [rt.jar:1.7.0_25]
--
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
12 years, 10 months
[JBoss JIRA] (WFLY-1673) Security Realms need a mechanism to allow querying of all known groups and users.
by Darran Lofthouse (JIRA)
[ https://issues.jboss.org/browse/WFLY-1673?page=com.atlassian.jira.plugin.... ]
Darran Lofthouse updated WFLY-1673:
-----------------------------------
Fix Version/s: 9.0.0.CR1
(was: 8.0.0.Beta1)
> Security Realms need a mechanism to allow querying of all known groups and users.
> ---------------------------------------------------------------------------------
>
> Key: WFLY-1673
> URL: https://issues.jboss.org/browse/WFLY-1673
> Project: WildFly
> Issue Type: Task
> Components: Domain Management, Security
> Reporter: Darran Lofthouse
> Assignee: Darran Lofthouse
> Priority: Critical
> Fix For: 9.0.0.CR1
>
>
> As part of the access control development we are adding the capability for users and groups to be associated with roles - for this to be most effective the admin tools need to be able to see the existing groups and users eligible for assignment.
> During authentication any queries executed are very targeted towards the currently authenticated user i.e. just searching for that users groups - now we need something to identify all users and groups.
--
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
12 years, 10 months
[JBoss JIRA] (WFLY-1721) Access log support
by Yoshimasa Tanabe (JIRA)
[ https://issues.jboss.org/browse/WFLY-1721?page=com.atlassian.jira.plugin.... ]
Yoshimasa Tanabe commented on WFLY-1721:
----------------------------------------
I have another question.
Does Undertow Access Log support response time(such as %D in Tomcat)?
(I maybe should ask this at Undertow space...)
I got the message that %D is not supported.
{code}
ERROR [io.undertow] (MSC service thread 1-2) UT005017: Unknown variable %D
{code}
I wonder that now Undetrow is not supported response time because there may be no attribute for it.
{code}
ls -l $UNDERTOW_REPO_ROOT/core/src/main/java/io/undertow/attribute | awk '{ print $9 }'
BytesSentAttribute.java
CompositeExchangeAttribute.java
ConstantExchangeAttribute.java
CookieAttribute.java
DateTimeAttribute.java
ExchangeAttribute.java
ExchangeAttributeBuilder.java
ExchangeAttributeParser.java
ExchangeAttributes.java
IdentUsernameAttribute.java
LocalIPAttribute.java
LocalPortAttribute.java
LocalServerNameAttribute.java
PredicateContextAttribute.java
QueryParameterAttribute.java
QueryStringAttribute.java
ReadOnlyAttributeException.java
RelativePathAttribute.java
RemoteIPAttribute.java
RemoteUserAttribute.java
RequestHeaderAttribute.java
RequestLineAttribute.java
RequestMethodAttribute.java
RequestProtocolAttribute.java
RequestURLAttribute.java
ResponseCodeAttribute.java
ResponseHeaderAttribute.java
SslCipherAttribute.java
SslClientCertAttribute.java
SslSessionIdAttribute.java
ThreadNameAttribute.java
{code}
> Access log support
> ------------------
>
> Key: WFLY-1721
> URL: https://issues.jboss.org/browse/WFLY-1721
> Project: WildFly
> Issue Type: Feature Request
> Components: Web (Undertow)
> Affects Versions: 8.0.0.Alpha3
> Reporter: Tomaz Cerar
> Assignee: Tomaz Cerar
> Fix For: 8.0.0.Beta1
>
>
> We need to expose access log configuration trough management.
--
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
12 years, 10 months
[JBoss JIRA] (AS7-1762) rewrite rule doesnt function
by Carl L (JIRA)
[ https://issues.jboss.org/browse/AS7-1762?page=com.atlassian.jira.plugin.s... ]
Carl L commented on AS7-1762:
-----------------------------
Hi, Carlos. I've haven't test in EAP but rewrite has been working fine for us with JBoss 7.1.1. We added {{flags="L"}} to our tag, but I'm not sure if that's significant in this case. Current rule:
{code}
<rewrite pattern="^/(.*)/([\w\-]+)$" substitution="/$1/$2.jsp" flags="L"/>
{code}
> rewrite rule doesnt function
> ----------------------------
>
> Key: AS7-1762
> URL: https://issues.jboss.org/browse/AS7-1762
> Project: Application Server 7
> Issue Type: Bug
> Components: Web
> Affects Versions: 7.0.1.Final
> Reporter: jefimm
> Assignee: Remy Maucherat
> Fix For: 7.1.0.Beta1
>
> Attachments: helloworld.war
>
>
> I have tried to add the following configuration to the standalone.xml <virtual-server> node:
> <virtual-server name="default-host">
> <alias name="localhost"/>
> <alias name="example.com"/>
> <rewrite pattern="^/helloworld(.*)" substitution="/helloworld/test.jsp"/>
> </virtual-server>
> and I have deployed the helloworld.war, however the rewrite does not work (I know I can deploy war at the root context I just want to test the rewrite).
--
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
12 years, 10 months
[JBoss JIRA] (AS7-1762) rewrite rule doesnt function
by Carl L (JIRA)
[ https://issues.jboss.org/browse/AS7-1762?page=com.atlassian.jira.plugin.s... ]
Carl L edited comment on AS7-1762 at 8/29/13 12:42 PM:
-------------------------------------------------------
Hi, Carlos. I've haven't tested in EAP but rewrite has been working fine for us with JBoss 7.1.1. We added {{flags="L"}} to our tag, but I'm not sure if that's significant in this case. Current rule:
{code}
<rewrite pattern="^/(.*)/([\w\-]+)$" substitution="/$1/$2.jsp" flags="L"/>
{code}
was (Author: scorcher14x):
Hi, Carlos. I've haven't test in EAP but rewrite has been working fine for us with JBoss 7.1.1. We added {{flags="L"}} to our tag, but I'm not sure if that's significant in this case. Current rule:
{code}
<rewrite pattern="^/(.*)/([\w\-]+)$" substitution="/$1/$2.jsp" flags="L"/>
{code}
> rewrite rule doesnt function
> ----------------------------
>
> Key: AS7-1762
> URL: https://issues.jboss.org/browse/AS7-1762
> Project: Application Server 7
> Issue Type: Bug
> Components: Web
> Affects Versions: 7.0.1.Final
> Reporter: jefimm
> Assignee: Remy Maucherat
> Fix For: 7.1.0.Beta1
>
> Attachments: helloworld.war
>
>
> I have tried to add the following configuration to the standalone.xml <virtual-server> node:
> <virtual-server name="default-host">
> <alias name="localhost"/>
> <alias name="example.com"/>
> <rewrite pattern="^/helloworld(.*)" substitution="/helloworld/test.jsp"/>
> </virtual-server>
> and I have deployed the helloworld.war, however the rewrite does not work (I know I can deploy war at the root context I just want to test the rewrite).
--
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
12 years, 10 months
[JBoss JIRA] (DROOLS-235) Issues with Drools Eclipse plugin
by Mario Fusco (JIRA)
[ https://issues.jboss.org/browse/DROOLS-235?page=com.atlassian.jira.plugin... ]
Mario Fusco resolved DROOLS-235.
--------------------------------
Resolution: Done
That further issue was caused by the new ClassLoader. I fixed it.
> Issues with Drools Eclipse plugin
> ---------------------------------
>
> Key: DROOLS-235
> URL: https://issues.jboss.org/browse/DROOLS-235
> Project: Drools
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Affects Versions: 6.0.0.CR2
> Reporter: Kris Verlaenen
> Assignee: Mario Fusco
> Fix For: 6.0.0.CR3
>
> Attachments: Screenshot1.png
>
>
> When generating a sample Drools project with the Eclipse plugin (6.0.x), there are several issues:
> * When DroolsBuilder is trying to parse the Sample.drl, it seems to be failing to import the Message class (resulting in 11 errors in the problems view), see screenshot1. Executing the test does seem to work though
> * When both Sample.drl and Sample.xls are created in the same project, the imports seems to clash, executing the test fails when compiling:
> java.lang.RuntimeException: Error while creating KieBase[Message [id=1, level=ERROR, path=rules/Sample.drl, line=15, column=0
> text=Rule Compilation error The import com.sample.DroolsTest.Message collides with another import statement], Message [id=2, level=ERROR, path=dtables/Sample.xls, line=15, column=0
> text=Rule Compilation error The import com.sample.DroolsTest.Message collides with another import statement], Message [id=3, level=ERROR, path=dtables/Sample.xls, line=5, column=0
> text=Rule Compilation error The import com.sample.DroolsTest.Message collides with another import statement], Message [id=4, level=ERROR, path=rules/Sample.drl, line=5, column=0
> text=Rule Compilation error The import com.sample.DroolsTest.Message collides with another import statement]]
> at org.drools.compiler.kie.builder.impl.KieContainerImpl.getKieBase(KieContainerImpl.java:170)
> at org.drools.compiler.kie.builder.impl.KieContainerImpl.newKieSession(KieContainerImpl.java:298)
> at org.drools.compiler.kie.builder.impl.KieContainerImpl.newKieSession(KieContainerImpl.java:273)
> at com.sample.DroolsTest.main(DroolsTest.java:17)
> Isn't this allowed?
> * When executing DroolsTest, there seems to be a Sysout somewhere in the code base:
> kmodules: file:/NotBackedUp/jBPM-6.0.0.CR2/jbpm-installer/workspace/drools/target/META-INF/kmodule.xml
--
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
12 years, 10 months
[JBoss JIRA] (WFLY-1967) Connection properties should be extracted automatically when creating a new Datasource
by Jesper Pedersen (JIRA)
[ https://issues.jboss.org/browse/WFLY-1967?page=com.atlassian.jira.plugin.... ]
Jesper Pedersen updated WFLY-1967:
----------------------------------
Labels: JDBC JDBC_connection open_to_community (was: JDBC JDBC_connection)
Assignee: (was: Jesper Pedersen)
Affects Version/s: (was: 8.0.0.Alpha4)
> Connection properties should be extracted automatically when creating a new Datasource
> --------------------------------------------------------------------------------------
>
> Key: WFLY-1967
> URL: https://issues.jboss.org/browse/WFLY-1967
> Project: WildFly
> Issue Type: Enhancement
> Components: JCA
> Reporter: Jay Wu
> Priority: Optional
> Labels: JDBC, JDBC_connection, open_to_community
>
> When create a new Datasource, it needs to input the connection properties such as databaseName, serverName, user, password etc even also the datasouce class manually.
> It should be enhanced for the ease for operation to extract the connection properties automatically when creating a new Datasource
--
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
12 years, 10 months