[JBoss JIRA] Created: (JBRULES-2639) Research Event Algebra: sequence, disjunction, conjunction, concurrent, xor, not, any, aperiodic, periodic
by Edson Tirelli (JIRA)
Research Event Algebra: sequence, disjunction, conjunction, concurrent, xor, not, any, aperiodic, periodic
----------------------------------------------------------------------------------------------------------
Key: JBRULES-2639
URL: https://jira.jboss.org/browse/JBRULES-2639
Project: Drools
Issue Type: Task
Security Level: Public (Everyone can see)
Affects Versions: 5.1.0.FINAL
Reporter: Edson Tirelli
Assignee: Edson Tirelli
Fix For: FUTURE
Research Event Algebra: sequence, disjunction, conjunction, concurrent, xor, not, any, aperiodic, periodic
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 9 months
[JBoss JIRA] Created: (AS7-1288) NPE in thread "vfs-shutdown"
by Juergen Zimmermann (JIRA)
NPE in thread "vfs-shutdown"
-----------------------------
Key: AS7-1288
URL: https://issues.jboss.org/browse/AS7-1288
Project: Application Server 7
Issue Type: Bug
Components: VFS
Affects Versions: 7.0.0.Final
Environment: 7.1.0.Alpha1 Jenkins build 1402
Reporter: Juergen Zimmermann
Assignee: John Bailey
When I shutdown a standalone server I'm getting a NPE. The shutdown command is:
jboss-admin.bat --connect command=:shutdown
Console log:
...
18:24:55,990 INFO [org.jboss.as.logging] Restored bootstrap log handlers
18:24:55,990 INFO [org.jboss.as.jmx.JMXConnectorService] JMX remote connector stopped
18:24:56,075 INFO [org.jboss.osgi.framework.internal.HostBundleState] Bundle stopped: jboss-as-osgi-configadmin:7.1.0.Alpha1-SNAPSHOT
18:24:56,125 INFO [org.jboss.osgi.framework.internal.HostBundleState] Bundle stopped: org.apache.felix.log:1.0.0
18:24:56,230 INFO [org.apache.catalina.core.StandardContext] Container org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/] has not been started
18:24:56,286 INFO [org.jboss.osgi.framework.internal.HostBundleState] Bundle stopped: org.apache.felix.configadmin:1.2.8
18:24:56,323 INFO [org.jboss.osgi.framework.internal.HostBundleState] Bundle stopped: jboss-osgi-logging:1.0.0
18:24:56,330 INFO [com.arjuna.ats.jbossatx] ARJUNA32018: Destroying TransactionManagerService
18:24:56,331 INFO [com.arjuna.ats.jbossatx] ARJUNA32014: Stopping transaction recovery manager
18:24:56,368 ERROR [stderr] Exception in thread "vfs-shutdown" java.lang.NullPointerException
18:24:56,368 ERROR [stderr] at org.jboss.vfs.TempFileProvider$DeleteTask.run(TempFileProvider.java:151)
18:24:56,368 ERROR [stderr] at org.jboss.vfs.TempFileProvider.close(TempFileProvider.java:132)
18:24:56,368 ERROR [stderr] at org.jboss.osgi.vfs30.VirtualFileAdaptor30$2.run(VirtualFileAdaptor30.java:94)
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 9 months
[JBoss JIRA] (AS7-2941) Problem deploying grails app
by Idar Borlaug (Created) (JIRA)
Problem deploying grails app
----------------------------
Key: AS7-2941
URL: https://issues.jboss.org/browse/AS7-2941
Project: Application Server 7
Issue Type: Bug
Affects Versions: 7.1.0.Beta1
Environment: Grails 1.3.4
Reporter: Idar Borlaug
Trying to deploy a grails 1.3.4 app on jboss 7.1.0.Beta1
The same app works fine on jboss 4.
12:26:44,722 ERROR [byfjell] (Thread-59) FrameworkEvent ERROR: org.apache.felix.log.LogException: org.osgi.framework.BundleException: Cannot resolve bundle resModule: [byfjell:0.1.0]
at org.jboss.osgi.framework.internal.ResolverPlugin.resolve(ResolverPlugin.java:157)
at org.jboss.osgi.framework.internal.AbstractBundleState.ensureResolved(AbstractBundleState.java:551)
at org.jboss.osgi.framework.internal.HostBundleState.startInternal(HostBundleState.java:211)
at org.jboss.osgi.framework.internal.AbstractBundleState.start(AbstractBundleState.java:494)
at org.jboss.as.osgi.deployment.BundleStartTracker$1.processService(BundleStartTracker.java:144)
at org.jboss.as.osgi.deployment.BundleStartTracker$1.transition(BundleStartTracker.java:119)
at org.jboss.msc.service.ServiceControllerImpl.invokeListener(ServiceControllerImpl.java:1429)
at org.jboss.msc.service.ServiceControllerImpl.access$2600(ServiceControllerImpl.java:49)
at org.jboss.msc.service.ServiceControllerImpl$ListenerTask.run(ServiceControllerImpl.java:1952)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) [:1.6.0_22]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) [:1.6.0_22]
at java.lang.Thread.run(Thread.java:679) [:1.6.0_22]
Caused by: org.apache.felix.log.LogException: org.jboss.osgi.resolver.XResolverException: Unable to resolve Module[byfjell:0.1.0]: missing requirement [Module[byfjell:0.1.0]] package; (&(package=javax.servlet)(version>=2.4.0)(!(version>=3.0.0)))
at org.jboss.osgi.resolver.felix.FelixResolver.resolveInternal(FelixResolver.java:117)
at org.jboss.osgi.resolver.spi.AbstractResolver.resolve(AbstractResolver.java:148)
at org.jboss.osgi.framework.internal.ResolverPlugin.resolve(ResolverPlugin.java:155)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 9 months
[JBoss JIRA] (AS7-4956) Deployed JMS destinations are not manageable
by Jeff Mesnil (JIRA)
Jeff Mesnil created AS7-4956:
--------------------------------
Summary: Deployed JMS destinations are not manageable
Key: AS7-4956
URL: https://issues.jboss.org/browse/AS7-4956
Project: Application Server 7
Issue Type: Bug
Components: JMS
Reporter: Jeff Mesnil
Assignee: Jeff Mesnil
1.deploy the helloworld-mdb quickstart
=> this deploys a HELLOWORLDMDBQueue JMS Queue from its webapp/WEB-INF/hornetq-jms.xml
2. this JMS queue is not exposed in the admin CLI or web console
$ ./bin/jboss-cli.sh --connect
[standalone@localhost:9999 /] /subsystem=messaging/hornetq-server=default/jms-queue=HELLOWORLDMDBQueue:read-resource
{
"outcome" => "failed",
"failure-description" => "JBAS014807: Management resource '[
(\"subsystem\" => \"messaging\"),
(\"hornetq-server\" => \"default\"),
(\"jms-queue\" => \"HELLOWORLDMDBQueue\")
]' not found",
"rolled-back" => true
}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 9 months
[JBoss JIRA] Created: (JBRULES-3163) Drools does not work with Java7
by Andreas Pieber (JIRA)
Drools does not work with Java7
-------------------------------
Key: JBRULES-3163
URL: https://issues.jboss.org/browse/JBRULES-3163
Project: Drools
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: drools-compiler
Affects Versions: 5.2.0.Final, 5.1.1.FINAL
Reporter: Andreas Pieber
Assignee: Mark Proctor
Fix For: 5.2.1.Final, 5.3.0.Beta1
While there are various places where 1.7 for java source version is already used it seams that there are some places where it simply had been forgotten.
It would be very great if that pull request could make it into a very soon 5.2.1.FINAL release since java7 is released now.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 9 months