[JBoss JIRA] Created: (JBAS-9335) Errors in windows service.bat error handling
by Stephen Parry (JIRA)
Errors in windows service.bat error handling
--------------------------------------------
Key: JBAS-9335
URL: https://issues.jboss.org/browse/JBAS-9335
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: MSC
Affects Versions: 6.0.0.Final
Environment: Windows
Reporter: Stephen Parry
Priority: Minor
service.bat
The errorlevel handling in the service.bat script is incorrect causing misleading error messages.
The syntax:
if errorlevel 1
is used meaning "if errorlevel == 1", when it actual means "if errorlevel >= 1". The syntax that should be used is:
if %errorlevel% EQU 1
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 11 months
[JBoss JIRA] Created: (JBRULES-2487) NPE on line 69 of ConcurrentNodeMemories.java when calling JPAKnowledgeService.loadStatefulKnowledgeSession
by hoogenbj (JIRA)
NPE on line 69 of ConcurrentNodeMemories.java when calling JPAKnowledgeService.loadStatefulKnowledgeSession
-----------------------------------------------------------------------------------------------------------
Key: JBRULES-2487
URL: https://jira.jboss.org/jira/browse/JBRULES-2487
Project: Drools
Issue Type: Bug
Security Level: Public (Everyone can see)
Environment: JBoss 4.2.3, Java 6 64-bit, Windows Vista 64-bit
Reporter: hoogenbj
Assignee: Mark Proctor
Hi,
I get a NullPointerException on line 69 of ConcurrentNodeMemories when calling JPAKnowledgeService.loadStatefulKnowledgeSession(...) in order to complete a work item using session.getWorkItemManager().completeWorkItem(...).
Further investigation reveals that the objectType on line 332 of InputMarshaller refers to one of my objects that I passed as part of the second argument object when calling startProcess on the knowledge session that I got with JPAKnowledgeService.newStatefulKnowledgeSession. The objectTypeNode on line 333 of InputMarshaller is null which eventually causes the NPE in ConcurrentNodeMemories.
This error does not occurr when starting and completing the whole process without retrieving the session from the database. Which seems to indicate that something is not persisted or correctly retrieved from the database.
This is a serious problem for us. It means we have to find an alternative for Drools flow...
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 11 months
[JBoss JIRA] Created: (JBLOGGING-51) jboss-logging-spi in OSGI
by luca stancapiano (JIRA)
jboss-logging-spi in OSGI
-------------------------
Key: JBLOGGING-51
URL: https://issues.jboss.org/browse/JBLOGGING-51
Project: JBoss Logging
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Environment: felix
Reporter: luca stancapiano
Assignee: David Lloyd
I'ld like jboss-logging-spi be a OSGI bundle so it can be installed in all OSGI repositories. Actually I tested it with felix. To do it it is enough add this plugin configuration in the pom.xml:
<!-- It configures the package to use inside a OSGI repository -->
<plugin>
<groupId>org.apache.felix</groupId>
<artifactId>maven-bundle-plugin</artifactId>
<version>2.1.0</version>
<extensions>true</extensions>
<configuration>
<instructions>
<Bundle-DocURL>http://community.jboss.org/wiki/JBossCommonProject</Bundle-DocURL>
<Export-Package>
${project.groupId}.*;version=${project.version};-split-package:=error
</Export-Package>
</instructions>
</configuration>
</plugin>
and modify the <packaging> row from 'jar' to 'bundle' so:
<packaging>bundle</packaging>
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 11 months
[JBoss JIRA] Created: (JBAS-8836) org.jboss.test.web.test.RootContextUnitTestCase
by Shelly McGowan (JIRA)
org.jboss.test.web.test.RootContextUnitTestCase
-----------------------------------------------
Key: JBAS-8836
URL: https://issues.jboss.org/browse/JBAS-8836
Project: JBoss Application Server
Issue Type: Sub-task
Security Level: Public (Everyone can see)
Components: Test Suite
Reporter: Shelly McGowan
Assignee: Shelly McGowan
Fix For: 6.0.1
org.jboss.test.web.test.RootContextUnitTestCase.testRootContextEAR
org.jboss.test.web.test.RootContextUnitTestCase.testRootContextWAR
2011-01-24 05:41:05,869 DEBUG [org.jboss.web.tomcat.service.deployers.TomcatDeployment] (RMI TCP Connection(606)-10.16.93.209) Linking security/securityMgr to JNDI name: java:/jaas/jboss-web-policy
2011-01-24 05:41:05,869 ERROR [org.jboss.web.tomcat.service.deployers.TomcatDeployment] (RMI TCP Connection(606)-10.16.93.209) ENC setup failed: javax.naming.NameAlreadyBoundException: securityMgr
at org.jnp.server.NamingServer.bind(NamingServer.java:209) [:5.0.5.Final]
at org.jnp.server.NamingServer.bind(NamingServer.java:167) [:5.0.5.Final]
at org.jnp.server.NamingServer.bind(NamingServer.java:167) [:5.0.5.Final]
at org.jnp.interfaces.NamingContext.bind(NamingContext.java:652) [:5.0.5.Final]
at org.jnp.interfaces.NamingContext.bind(NamingContext.java:613) [:5.0.5.Final]
at org.jboss.util.naming.Util.bind(Util.java:105) [jboss-common-core.jar:2.2.17.GA]
at org.jboss.util.naming.Util.bind(Util.java:91) [jboss-common-core.jar:2.2.17.GA]
at org.jboss.web.deployers.AbstractWarDeployment.linkSecurityDomain(AbstractWarDeployment.java:836) [:6.0.1-SNAPSHOT]
at org.jboss.web.tomcat.service.deployers.TomcatDeployment.access$200(TomcatDeployment.java:85) [:6.0.1-SNAPSHOT]
at org.jboss.web.tomcat.service.deployers.TomcatDeployment$EncListener.lifecycleEvent(TomcatDeployment.java:437) [:6.0.1-SNAPSHOT]
at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:115) [:]
at org.apache.catalina.core.StandardContext.start(StandardContext.java:3823) [:]
at org.jboss.web.tomcat.service.deployers.TomcatDeployment.performDeployInternal(TomcatDeployment.java:294) [:6.0.1-SNAPSHOT]
at org.jboss.web.tomcat.service.deployers.TomcatDeployment.performDeploy(TomcatDeployment.java:146) [:6.0.1-SNAPSHOT]
at org.jboss.web.deployers.AbstractWarDeployment.start(AbstractWarDeployment.java:477) [:6.0.1-SNAPSHOT]
at org.jboss.web.deployers.WebModule.startModule(WebModule.java:118) [:6.0.1-SNAPSHOT]
at org.jboss.web.deployers.WebModule.start(WebModule.java:95) [:6.0.1-SNAPSHOT]
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 11 months
[JBoss JIRA] Created: (JBAS-8739) org.jboss.test.profileservice.test.Ejb3MetricsUnitTestCase
by Shelly McGowan (JIRA)
org.jboss.test.profileservice.test.Ejb3MetricsUnitTestCase
----------------------------------------------------------
Key: JBAS-8739
URL: https://issues.jboss.org/browse/JBAS-8739
Project: JBoss Application Server
Issue Type: Sub-task
Security Level: Public (Everyone can see)
Reporter: Shelly McGowan
Assignee: Andrew Rubinger
Fix For: 6.0.0.Final
All tests failing:
testEarManagedComponentNames
testMdb
testSfsb
testSlsb
testSlsbLocal
with:
Component not found; no managed object with name "testEjb3xMetrics.jar/BEAN" in: []
Stacktrace
junit.framework.AssertionFailedError: Component not found; no managed object with name "testEjb3xMetrics.jar/SLSB" in: []
at org.jboss.test.profileservice.test.Ejb3MetricsUnitTestCase.getAndTestManagedComponent(Ejb3MetricsUnitTestCase.java:453)
at org.jboss.test.profileservice.test.Ejb3MetricsUnitTestCase.testSlsb(Ejb3MetricsUnitTestCase.java:255)
These tests were passing with EJB 3 depchain 1.0.0-alpha-32 and failing with 1.0.0-alpha-34 (do not have results of these tests with 1.0.0-alpha-33)
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 11 months