[JBoss JIRA] Created: (GPD-384) Broken NON-LATIN characters in project/node names/values after saving process JPDL XML file
by Konstantin Kasatkin (JIRA)
Broken NON-LATIN characters in project/node names/values after saving process JPDL XML file
-------------------------------------------------------------------------------------------
Key: GPD-384
URL: https://jira.jboss.org/jira/browse/GPD-384
Project: jBPM GPD
Issue Type: Patch
Components: jpdl
Affects Versions: jBPM jPDL Designer 4.2
Environment: Windows XP x32
Reporter: Konstantin Kasatkin
Assignee: Koen Aers
Priority: Critical
Fix For: jBPM jPDL Designer 4.x, jBPM jPDL Designer 4.2
When we populate any attribute in JPDL XML with NON-LATIN characters Editor reads it correctly displays all atributes in proper characterset.
When we change any attribute in GUI mode and save changes all characters became unreadable (sometimes just "???").
It happens due to missing implicit pointing characterset in the method that constructs OutputStreamWriter.
As the XML has hardcoded UTF-8 encoding at saving time it reasonable to change a peace of code like:
new OutputStreamWriter(os)
to
new OutputStreamWriter(os, "UTF-8");
--
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
16 years
[JBoss JIRA] Created: (GPD-380) custom activity child nodes being deleted
by Kevin Elliott (JIRA)
custom activity child nodes being deleted
-----------------------------------------
Key: GPD-380
URL: https://jira.jboss.org/jira/browse/GPD-380
Project: jBPM GPD
Issue Type: Bug
Affects Versions: jBPM jPDL Designer 4.2, jBPM jPDL Designer 4.1, jBPM jPDL Designer 4.0.0.GA
Reporter: Kevin Elliott
Assignee: Koen Aers
if you have a custom activity that has <field> child nodes and you update the process diagram, all of the field child nodes in all custom activities are deleted.
for example -
<custom expr="#{sendMuleEventAndContinue}" g="292,687,92,52" name="validate">
<field name="endpoint"><string value="validateEndpoint"/></field>
<field name="payloadSource"><string value="incoming"/></field>
<field name="synchronous"><true/></field>
<transition g="-124,-8" name="to postValidation" to="postValidation"/>
</custom>
becomes -
<custom expr="#{sendMuleEventAndContinue}" g="292,687,92,52" name="validate">
<transition g="-124,-8" name="to postValidation" to="postValidation"/>
</custom>
--
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
16 years
[JBoss JIRA] Created: (JBAS-7565) Could Not Deploy the EJB 3 bean JBoss
by Navaneetha krishnan Balakrishnan (JIRA)
Could Not Deploy the EJB 3 bean JBoss
--------------------------------------
Key: JBAS-7565
URL: https://jira.jboss.org/jira/browse/JBAS-7565
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: EJB3
Affects Versions: JBossAS-5.1.0.GA
Environment: Windows
Reporter: Navaneetha krishnan Balakrishnan
Assignee: Carlo de Wolf
Fix For: JBossAS-5.1.0.GA
2009-12-18 14:16:40,636 ERROR [org.jboss.ejb3.Ejb3Deployment] (main) Exception while processing container metadata for EJB: SystemControlBean in unit: PDBcacontrol.jar
2009-12-18 14:16:40,652 ERROR [org.jboss.kernel.plugins.dependency.AbstractKernelController] (main) Error installing to Real: name=vfszip:/C:/development/jboss-5.1.1/server/prodb/deploy/pdb.ear/ state=PreReal mode=Manual requiredState=Real
org.jboss.deployers.spi.DeploymentException: Error deploying PDBcacontrol.jar: Exception while processing container metadata for EJB: SystemControlBean in unit: PDBcacontrol.jar
at org.jboss.ejb3.deployers.Ejb3Deployer.deploy(Ejb3Deployer.java:196)
at org.jboss.ejb3.deployers.Ejb3Deployer.deploy(Ejb3Deployer.java:99)
at org.jboss.deployers.vfs.spi.deployer.AbstractVFSRealDeployer.internalDeploy(AbstractVFSRealDeployer.java:45)
at org.jboss.deployers.spi.deployer.helpers.AbstractRealDeployer.deploy(AbstractRealDeployer.java:50)
at org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:171)
at org.jboss.deployers.plugins.deployers.DeployersImpl.doDeploy(DeployersImpl.java:1439)
at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:1157)
at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:1210)
at org.jboss.deployers.plugins.deployers.DeployersImpl.install(DeployersImpl.java:1098)
at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:348)
at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1631)
at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:934)
at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1082)
at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:984)
at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:822)
at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:553)
at org.jboss.deployers.plugins.deployers.DeployersImpl.process(DeployersImpl.java:781)
at org.jboss.deployers.plugins.main.MainDeployerImpl.process(MainDeployerImpl.java:702)
at org.jboss.system.server.profileservice.repository.MainDeployerAdapter.process(MainDeployerAdapter.java:117)
at org.jboss.system.server.profileservice.repository.ProfileDeployAction.install(ProfileDeployAction.java:70)
at org.jboss.system.server.profileservice.repository.AbstractProfileAction.install(AbstractProfileAction.java:53)
at org.jboss.system.server.profileservice.repository.AbstractProfileService.install(AbstractProfileService.java:361)
at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:348)
at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1631)
at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:934)
at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1082)
at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:984)
at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:822)
at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:553)
at org.jboss.system.server.profileservice.repository.AbstractProfileService.activateProfile(AbstractProfileService.java:306)
at org.jboss.system.server.profileservice.ProfileServiceBootstrap.start(ProfileServiceBootstrap.java:271)
at org.jboss.bootstrap.AbstractServerImpl.start(AbstractServerImpl.java:461)
at org.jboss.Main.boot(Main.java:221)
at org.jboss.Main$1.run(Main.java:556)
at java.lang.Thread.run(Thread.java:595)
Caused by: java.lang.Exception: Exception while processing container metadata for EJB: SystemControlBean in unit: PDBcacontrol.jar
at org.jboss.ejb3.Ejb3Deployment.start(Ejb3Deployment.java:549)
at org.jboss.ejb3.deployers.Ejb3Deployer.deploy(Ejb3Deployer.java:189)
... 34 more
Caused by: java.lang.IllegalStateException: JBAS-5713: could not find an ejb3 deployment for system.jar (yet), try reordering the jars or adding explicit dependencies
at org.jboss.ejb3.deployers.JBoss5DeploymentScope.getEjbContainer(JBoss5DeploymentScope.java:173)
at org.jboss.ejb3.Ejb3Deployment.getEjbContainer(Ejb3Deployment.java:410)
at org.jboss.ejb3.EJBContainer.resolveEjbContainer(EJBContainer.java:1418)
at org.jboss.injection.AbstractHandler.addDependency(AbstractHandler.java:50)
at org.jboss.injection.EJBRemoteHandler.ejbRefDependency(EJBRemoteHandler.java:146)
at org.jboss.injection.EJBRemoteHandler.handleFieldAnnotations(EJBRemoteHandler.java:393)
at org.jboss.injection.InjectionUtil.processFieldAnnotations(InjectionUtil.java:160)
at org.jboss.injection.InjectionUtil.processAnnotations(InjectionUtil.java:197)
at org.jboss.ejb3.EJBContainer.processMetadata(EJBContainer.java:590)
at org.jboss.ejb3.Ejb3Deployment.processEJBContainerMetadata(Ejb3Deployment.java:418)
at org.jboss.ejb3.Ejb3Deployment.start(Ejb3Deployment.java:527)
... 35 more
2009-12-18 14:16:40,917 ERROR [org.jboss.system.server.profileservice.ProfileServiceBootstrap] (main) Failed to load profile: Summary of incomplete deployments (SEE PREVIOUS ERRORS FOR DETAILS):
DEPLOYMENTS IN ERROR:
Deployment "vfszip:/C:/development/jboss-5.1.1/server/prodb/deploy/pdb.ear/" is in error due to the following reason(s): java.lang.IllegalStateException: JBAS-5713: could not find an ejb3 deployment for system.jar (yet), try reordering the jars or adding explicit dependencies
2009-12-18 14:16:40,949 INFO [org.apache.coyote.http11.Http11Protocol] (main) Starting Coyote HTTP/1.1 on http-127.0.0.1-8180
2009-12-18 14:16:40,980 INFO [org.apache.coyote.ajp.AjpProtocol] (main) Starting Coyote AJP/1.3 on ajp-127.0.0.1-8109
2009-12-18 14:16:40,995 INFO [org.jboss.bootstrap.microcontainer.ServerImpl] (main) JBoss (Microcontainer) [5.1.0.GA (build: SVNTag=JBoss_5_1_0_GA date=200905221053)] Started in 1m:58s:561ms
--
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
16 years, 1 month
[JBoss JIRA] Created: (JBCL-137) Add support for OSGi Fragments
by Thomas Diesler (JIRA)
Add support for OSGi Fragments
------------------------------
Key: JBCL-137
URL: https://jira.jboss.org/jira/browse/JBCL-137
Project: JBoss ClassLoader
Issue Type: Feature Request
Reporter: Thomas Diesler
Fragments are bundles that can be attached to one or more host bundles by the
Framework. Attaching is done as part of resolving: the Framework appends
the relevant definitions of the fragment bundles to the host's definitions
before the host is resolved. Fragments are therefore treated as part of the
host, including any permitted headers; they must not have their own class
loader though fragments must have their own Protection Domain.
When attaching a fragment bundle to a host bundle the Framework must
perform the following steps:
1 Append the import definitions for the Fragment bundle that do not con-
flict with an import definition of the host to the import definitions of the
host bundle. A Fragment can provide an import statement for a private
package of the host. The private package in the host is hidden in that
case.
2 Append the Require-Bundle entries of the fragment bundle that do not
conflict with a Require-Bundle entry of the host to the Require-Bundle
entries of the host bundle.
3 Append the export definitions of a Fragment bundle to the export defini-
tions of the host bundle unless the exact definition (directives and
attributes must match) is already present in the host. Fragment bundles
can therefore add additional exports for the same package name. The
bundle-version attributes and bundle-symbolic-name attributes will
reflect the host bundle.
A host and a fragment conflict when they cannot resolve to provide a consis-
tent class space. If a conflict is found, the Fragment bundle is not attached to
the host bundle.
A Fragment bundle must enter the resolved state only if it has been success-
fully attached to at least one host bundle.
During runtime, the fragment's JAR is searched after the host's bundle class
path
--
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
16 years, 1 month
[JBoss JIRA] Created: (JBREM-981) CLONE [JBREM-980] - ServerInvokerServlet should retrieve ServletServerInvoker based on updated InvokerLocator
by Ron Sigal (JIRA)
CLONE [JBREM-980] - ServerInvokerServlet should retrieve ServletServerInvoker based on updated InvokerLocator
-------------------------------------------------------------------------------------------------------------
Key: JBREM-981
URL: http://jira.jboss.com/jira/browse/JBREM-981
Project: JBoss Remoting
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: 2.4.0.CR2
Reporter: Ron Sigal
Assigned To: Ron Sigal
Fix For: 2.4.0.GA
>From Galder:
Consider
<servlet>
<servlet-name>Ejb3ServerInvokerServlet</servlet-name>
<description>The ServerInvokerServlet receives requests via HTTP
protocol from within a web container and passes it onto the
ServletServerInvoker for processing.
</description>
<servlet-class>org.jboss.remoting.transport.servlet.web.ServerInvokerServlet</servlet-class>
<init-param>
<param-name>locatorUrl</param-name>
<param-value>servlet://${jboss.bind.address}:8080/unified-invoker/Ejb3ServerInvokerServlet</param-value>
<description>The servlet server invoker</description>
</init-param>
<load-on-startup>1</load-on-startup>
</servlet>
Now, let's say you bind to 0.0.0.0. You'll get an exception like this:
13:39:26,856 ERROR [ContainerBase] Servlet /unified-invoker threw load() exception
javax.servlet.ServletException: Can not find servlet server invoker with same locator as specified (servlet://0.0.0.0:8080/unified-invoker/Ejb3ServerInvokerServlet)
at org.jboss.remoting.transport.servlet.web.ServerInvokerServlet.getInvokerFromInvokerUrl(ServerInvokerServlet.java:198)
at org.jboss.remoting.transport.servlet.web.ServerInvokerServlet.init(ServerInvokerServlet.java:66)
The problem arises from the fact that Remoting is trying to compare:
servlet://0.0.0.0:8080/unified-invoker/Ejb3ServerInvokerServlet
with
servlet://localhost.localdomain:8080/unified-invoker/Ejb3ServerInvokerServlet
So either, ServerInvokerServlet should call ServerInvoker.validateLocator() with locatorUrl, take the return of that and compare that with the list of locators.
Or validateLocator() is modified to have the real original host passed to the InvokerLocator constructor, rather than the transformed or newHost.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
16 years, 1 month
[JBoss JIRA] Created: (JBRULES-2375) Drools hangs when events are retracted
by Paul O'Riordan (JIRA)
Drools hangs when events are retracted
--------------------------------------
Key: JBRULES-2375
URL: https://jira.jboss.org/jira/browse/JBRULES-2375
Project: Drools
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: drools-core (fusion)
Affects Versions: 5.0.1.FINAL
Environment: Java(TM) SE Runtime Environment (build 1.6.0_17-b04)
Microsoft Windows XP [Version 5.1.2600]
Intel (R) Xeon (R) CPU E5405 @ 2.00GHz (Quad Core)
Reporter: Paul O'Riordan
Assignee: Mark Proctor
Attachments: Main.java
Using a StatefulKnowledgeSession (stream mode). Drools hangs when events are retracted from the session. Running the attached code results in drools hanging almost immediately. Adding the @expires property to the event declaration, e.g.
declare Foo
@role (event)
@expires (10s)
end
causes drools to hang after the specified expiry time, i.e. 10 seconds.
--
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
16 years, 1 month
[JBoss JIRA] Created: (JBRULES-1888) Concurrency issue in MultithreadedTest
by Mark Proctor (JIRA)
Concurrency issue in MultithreadedTest
--------------------------------------
Key: JBRULES-1888
URL: https://jira.jboss.org/jira/browse/JBRULES-1888
Project: JBoss Drools
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: drools-compiler, drools-compiler (expert)
Reporter: Mark Proctor
Assignee: Edson Tirelli
Fix For: 5.0.0.CR1
MultithreadedTest.restRuleBaseConcurrentCreation sometimes has this error:
java.util.ConcurrentModificationException
at java.util.HashMap$HashIterator.nextEntry(HashMap.java:793)
at java.util.HashMap$ValueIterator.next(HashMap.java:822)
at org.drools.reteoo.EntryPointNode.updateSink(EntryPointNode.java:283)
at org.drools.reteoo.ObjectTypeNode.attach(ObjectTypeNode.java:276)
at org.drools.reteoo.builder.PatternBuilder.attachObjectTypeNode(PatternBuilder.java:186)
at org.drools.reteoo.ClassObjectTypeConf.<init>(ClassObjectTypeConf.java:94)
at org.drools.common.ObjectTypeConfigurationRegistry.getObjectTypeConf(ObjectTypeConfigurationRegistry.java:58)thread-6 failed: null
at org.drools.reteoo.Rete.assertObject(Rete.java:109)
at org.drools.reteoo.ReteooRuleBase.assertObject(ReteooRuleBase.java:207)
at org.drools.reteoo.ReteooWorkingMemory$WorkingMemoryReteAssertAction.execute(ReteooWorkingMemory.java:275)
at org.drools.common.AbstractWorkingMemory.executeQueuedActions(AbstractWorkingMemory.java:1398)
at org.drools.common.AbstractWorkingMemory.insert(AbstractWorkingMemory.java:1005)
at org.drools.common.AbstractWorkingMemory.insert(AbstractWorkingMemory.java:968)
at org.drools.common.AbstractWorkingMemory.insert(AbstractWorkingMemory.java:740)
at org.drools.integrationtests.MultithreadTest$RulebaseRunner.run(MultithreadTest.java:125)
at java.lang.Thread.run(Thread.java:619)
--
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
16 years, 1 month