[JBoss JIRA] Created: (JBWEB-195) AS7 Startup problem - Could not initialize class org.apache.tomcat.jni.OS
by Krzysztof Maslak (JIRA)
AS7 Startup problem - Could not initialize class org.apache.tomcat.jni.OS
-------------------------------------------------------------------------
Key: JBWEB-195
URL: https://issues.jboss.org/browse/JBWEB-195
Project: JBoss Web
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Core
Affects Versions: JBossWeb-7.0.0.Beta1
Environment: Fedora 13 2.6.34.7-66.fc13.i686
java version "1.6.0_20"
Java(TM) SE Runtime Environment (build 1.6.0_20-b02)
Java HotSpot(TM) Server VM (build 16.3-b01, mixed mode)
Reporter: Krzysztof Maslak
Assignee: Remy Maucherat
Problem occurs during JBoss startup. Problem appeared after upgrading JBoss Web from version 3.0.0-beta-7 to 7.0.0.Beta1.
16:43:00,465 ERROR [org.jboss.msc] (pool-1-thread-3) MSC-00001: Failed to start service jboss.web.connector.http: org.jboss.msc.service.StartException in service jboss.web.connector.http: Failed to start service
at org.jboss.msc.service.ServiceInstanceImpl$StartTask.run(ServiceInstanceImpl.java:1207)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [:1.6.0_20]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [:1.6.0_20]
at java.lang.Thread.run(Thread.java:619) [:1.6.0_20]
Caused by: java.lang.NoClassDefFoundError: Could not initialize class org.apache.tomcat.jni.OS
at org.apache.tomcat.util.net.AprEndpoint.init(AprEndpoint.java:573)
at org.apache.coyote.http11.Http11AprProtocol.init(Http11AprProtocol.java:115)
at org.apache.catalina.connector.Connector.initialize(Connector.java:1018)
at org.apache.catalina.core.StandardService.addConnector(StandardService.java:351)
at org.jboss.as.web.WebServerService.addConnector(WebServerService.java:124)
at org.jboss.as.web.WebConnectorService.start(WebConnectorService.java:90)
at org.jboss.msc.service.ServiceInstanceImpl$StartTask.run(ServiceInstanceImpl.java:1163)
... 3 more
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 3 months
[JBoss JIRA] Created: (JBRULES-2896) NPE when AbortWorkItem
by Cristiano Nicolai (JIRA)
NPE when AbortWorkItem
----------------------
Key: JBRULES-2896
URL: https://issues.jboss.org/browse/JBRULES-2896
Project: Drools
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: drools-core
Affects Versions: 5.2.0.M1
Environment: JbossAS 5.1
MySQL 5.0.77
Reporter: Cristiano Nicolai
Assignee: Mark Proctor
AbortWorkItem method should test if WorkItemInfo inst null before merge. Basically is the same behaviour as completeWorkItem.
I'm getting the following exception when a Work Item is aborted:
2011-02-10 16:52:37,282 ERROR [org.drools.persistence.SingleSessionCommandService] (NioProcessor-3) Could not commit session
java.lang.IllegalArgumentException: attempt to create merge event with null entity
at org.hibernate.event.MergeEvent.<init>(MergeEvent.java:60)
at org.hibernate.event.MergeEvent.<init>(MergeEvent.java:43)
at org.hibernate.impl.SessionImpl.merge(SessionImpl.java:690)
at org.hibernate.impl.SessionImpl.merge(SessionImpl.java:694)
at org.hibernate.ejb.AbstractEntityManagerImpl.merge(AbstractEntityManagerImpl.java:235)
at org.drools.persistence.jpa.JpaPersistenceContext.merge(JpaPersistenceContext.java:49)
at org.drools.persistence.jpa.processinstance.JPAWorkItemManager.abortWorkItem(JPAWorkItemManager.java:136)
at org.drools.command.runtime.process.AbortWorkItemCommand.execute(AbortWorkItemCommand.java:56)
at org.drools.command.runtime.process.AbortWorkItemCommand.execute(AbortWorkItemCommand.java:29)
at org.drools.persistence.SingleSessionCommandService.execute(SingleSessionCommandService.java:295)
at org.drools.command.impl.CommandBasedStatefulKnowledgeSession$1.abortWorkItem(CommandBasedStatefulKnowledgeSession.java:152)
at org.jbpm.process.workitem.wsht.CommandBasedWSHumanTaskHandler$GetCompletedTaskResponseHandler.execute(CommandBasedWSHumanTaskHandler.java:245)
at org.jbpm.task.service.TaskClientHandler.messageReceived(TaskClientHandler.java:81)
at org.jbpm.task.service.mina.MinaTaskClientHandler.messageReceived(MinaTaskClientHandler.java:47)
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 3 months
[JBoss JIRA] Created: (JBAS-8608) Launch from path with space does not work
by Max Andersen (JIRA)
Launch from path with space does not work
-----------------------------------------
Key: JBAS-8608
URL: https://jira.jboss.org/browse/JBAS-8608
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: 7.0.0.Alpha1
Reporter: Max Andersen
Priority: Critical
Having a space in your download/install dir causes problem on AS 7(common on Mac for those forgetting to set simple username or on windows where "Documents and Settings" is the default - hence why I marked it critical ;):
mkdir "space launch"
cd "space launch"
unzip jboss-7.0.0.Alpha1
cd jboss-7.0.0.Alpha1
./bin/standalone.sh
=========================================================================
JBoss Bootstrap Environment
JBOSS_HOME: /Users/max/space launch/jboss-7.0.0.Alpha1
JAVA: java
JAVA_OPTS: -Xms64m -Xmx512m -XX:MaxPermSize=256m -Dorg.jboss.resolver.warning=true -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000
=========================================================================
Exception in thread "main" java.lang.NoClassDefFoundError: launch/jboss-7/0/0/Alpha1/standalone/log/boot/log
Caused by: java.lang.ClassNotFoundException: launch.jboss-7.0.0.Alpha1.standalone.log.boot.log
at java.net.URLClassLoader$1.run(URLClassLoader.java:202)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:190)
at java.lang.ClassLoader.loadClass(ClassLoader.java:307)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301)
at java.lang.ClassLoader.loadClass(ClassLoader.java:248)
--
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, 3 months
[JBoss JIRA] Created: (JBRULES-2672) Error while parsing xml with <and-constraint-connective> within <pattern>
by Veit Guna (JIRA)
Error while parsing xml with <and-constraint-connective> within <pattern>
-------------------------------------------------------------------------
Key: JBRULES-2672
URL: https://jira.jboss.org/browse/JBRULES-2672
Project: Drools
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: drools-compiler
Affects Versions: 5.1.0.FINAL
Environment: Jboss 5.1.0, Drools 5.1.0, Jdk 1.6.0_14
Reporter: Veit Guna
Assignee: Mark Proctor
Hi.
I'm using drools 5.1.0 together with .xdrl files. I encountered a possible bug in the AndHandler class when
parsing the following .xdrl file:
--cut here--
<dro:pattern object-type="EMail">
<dro:and-constraint-connective>
<dro:field-constraint field-name="foo">
<dro:literal-restriction evaluator="!=" value="null"/>
</dro:field-constraint>
<dro:field-constraint field-name="foo.toLowerCase">
<dro:literal-restriction evaluator="==" value="test"/>
</dro:field-constraint>
</dro:and-constraint-connective>
</dro:pattern>
--cut here--
Parsing this seems to fail when adding the package from xml:
Caused by: org.drools.compiler.DroolsParserException: org.xml.sax.SAXParseException: <and-constraint-connective> has an invalid parent element [[Pattern: id=null; objectType=EMail]]
at org.drools.compiler.PackageBuilder.addPackageFromXml(PackageBuilder.java:304)
at org.drools.compiler.PackageBuilder.addKnowledgeResource(PackageBuilder.java:468)
... 142 more
According to the .xsd (4.0) this should be no problem. Looking at the OrHandler it seems that simply the
PatternDescr is missing from the validParents.
Also tried to disable xml validation with:
System.setProperty("drools.schema.validating","false");
but with no luck. So find attached the _very_ complex patch that adds PackageDescr to the AndHandler :).
--
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, 3 months