April 2011 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBCL-131) Add a notion of on demand resolution

by Adrian Brock (JIRA)

Add a notion of on demand resolution ------------------------------------ Key: JBCL-131 URL: https://jira.jboss.org/jira/browse/JBCL-131 Project: JBoss ClassLoader Issue Type: Sub-task Components: Dependencies Reporter: Adrian Brock Assignee: Adrian Brock Fix For: JBossCL.2.0.9.GA , JBossCL.2.2.0.Alpha OSGi has a notion where a dependent classloader/bundle is not rcreated/resolved until somebody wants to import one of its exports. -- 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

15 years, 2 months

3
18
0 / 0

[JBoss JIRA] Created: (JBMETA-331) Infinite loop in JBossAppMetaDataParser

by Stuart Douglas (JIRA)

Infinite loop in JBossAppMetaDataParser --------------------------------------- Key: JBMETA-331 URL: https://issues.jboss.org/browse/JBMETA-331 Project: JBoss Metadata Issue Type: Bug Security Level: Public (Everyone can see) Components: ear Reporter: Stuart Douglas Priority: Critical JBossAppMetaDataParser goes into an infinite loop on line 143, as the next element is never read from the stream. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

2
3
0 / 0

[JBoss JIRA] Created: (AS7-692) Ability to modify server-group, subresource jvm

by Heiko Braun (JIRA)

Ability to modify server-group, subresource jvm ----------------------------------------------- Key: AS7-692 URL: https://issues.jboss.org/browse/AS7-692 Project: Application Server 7 Issue Type: Feature Request Components: Console Reporter: Heiko Braun Assignee: Heiko Braun Fix For: 7.0.0.Beta4 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

1
1
0 / 0

[JBoss JIRA] Created: (JBRULES-2976) DefaultMarshaller does not use supplied ObjectMarshallingStrategies

by Laird Nelson (JIRA)

DefaultMarshaller does not use supplied ObjectMarshallingStrategies ------------------------------------------------------------------- Key: JBRULES-2976 URL: https://issues.jboss.org/browse/JBRULES-2976 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-core (expert) Affects Versions: 5.2.0.M1, 5.2.0.M2, 5.2.0.CR1 Reporter: Laird Nelson Assignee: Mark Proctor DefaultMarshaller.java does not use the supplied ObjectMarshallingStrategy as far as I can tell. When you create a Marshaller like this: {code} final Marshaller marshaller = MarshallerFactory.newMarshaller(knowledgeBase, new ObjectMarshallingStrategy[] { myStrategy }); assert marshaller != null; {code} And then use it like this (or similar): {code} final ByteArrayOutputStream baos = new ByteArrayOutputStream(); final ObjectOutputStream oos = new ObjectOutputStream(baos); final DroolsObjectOutputStream doos = new DroolsObjectOutputStream(oos); marshaller.marshall(doos, this.droolsSession); {code} ...the supplied strategy's read() and write() methods are never called. This is because DefaultMarshaller.java line 132 does not use the DefaultMarshaller's strategy, but the strategy of the incoming StatefulKnowledgeSession instead. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

2
2
0 / 0

[JBoss JIRA] Created: (JBRULES-2796) NullPointerException in FromNode.destroyCreatedHandles

by Tommy Odom (JIRA)

NullPointerException in FromNode.destroyCreatedHandles ------------------------------------------------------ Key: JBRULES-2796 URL: https://jira.jboss.org/browse/JBRULES-2796 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-core Reporter: Tommy Odom Assignee: Mark Proctor I received this NullPointerException after upgrading to drools 5.1.1. The NullPointerException is being thrown when the rule executes "update($build);" where $build is set in the LHS from a Build in working memory. I'm not sure if the bug is that matches may be null and a null check needs to be added or if something else is going on causing the tuple to not be found. Caused by: java.lang.NullPointerException at org.drools.reteoo.FromNode.destroyCreatedHandles(FromNode.java:336) at org.drools.reteoo.FromNode.retractLeftTuple(FromNode.java:326) at org.drools.reteoo.CompositeLeftTupleSinkAdapter.doPropagateRetractLeftTuple(CompositeLeftTupleSinkAdapter.java:238) at org.drools.reteoo.CompositeLeftTupleSinkAdapter.propagateRetractRightTuple(CompositeLeftTupleSinkAdapter.java:155) at org.drools.reteoo.JoinNode.retractRightTuple(JoinNode.java:151) at org.drools.reteoo.ModifyPreviousTuples.retractTuples(ModifyPreviousTuples.java:126) at org.drools.reteoo.EntryPointNode.modifyObject(EntryPointNode.java:176) at org.drools.common.AbstractWorkingMemory.update(AbstractWorkingMemory.java:1442) at org.drools.common.AbstractWorkingMemory.update(AbstractWorkingMemory.java:1349) at org.drools.base.DefaultKnowledgeHelper.update(DefaultKnowledgeHelper.java:183) at org.drools.base.DefaultKnowledgeHelper.update(DefaultKnowledgeHelper.java:196) at buildSchedulerV2.Rule_Combine_Builds_0.defaultConsequence(Rule_Combine_Builds_0.java:36) at buildSchedulerV2.Rule_Combine_Builds_0DefaultConsequenceInvoker.evaluate(Rule_Combine_Builds_0DefaultConsequenceInvoker.java:49) at org.drools.common.DefaultAgenda.fireActivation(DefaultAgenda.java:917) -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

4
4
0 / 0

[JBoss JIRA] Created: (JBRULES-2899) Rewrite documentation Section-Checkout.xml after the split-up

by Geoffrey De Smet (JIRA)

Rewrite documentation Section-Checkout.xml after the split-up ------------------------------------------------------------- Key: JBRULES-2899 URL: https://issues.jboss.org/browse/JBRULES-2899 Project: Drools Issue Type: Task Security Level: Public (Everyone can see) Reporter: Geoffrey De Smet Priority: Minor The file Section-Checkout.xml in the introduction manual is totally out of date. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

1
2
0 / 0

[JBoss JIRA] Created: (JBAS-9275) JavaEE 5 annotated Webservice-EJB fails

by Rainer Flicker (JIRA)

JavaEE 5 annotated Webservice-EJB fails --------------------------------------- Key: JBAS-9275 URL: https://issues.jboss.org/browse/JBAS-9275 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 6.0.0.Final Environment: JBoss AS 6.0.0.Final JBoss Seam 2.2.1 Final Oracle JDK 1.6.24 Windows XP SP3 Reporter: Rainer Flicker A JavaEE 5 annotated Webservice-EJB (works with JBoss AS 5.1, Glassfish 2.1 and Websphere 7) fails with: Caused by: java.lang.LinkageError: loader constraint violation in interface itable initialization: when resolving method "$Proxy280.setElementType(Ljavax/xml/namespace/QName;)V" the class loader (instance of org/jboss/classloader/spi/base/BaseClassLoader) of the current class, $Proxy280, and the class loader (instance of org/jboss/classloader/spi/base/BaseClassLoader) for interface javax/wsdl/extensions/ExtensibilityElement have different Class objects for the type javax/xml/namespace/QName used in the signature at java.lang.Class.getDeclaredConstructors0(Native Method) [:1.6.0_24] at java.lang.Class.privateGetDeclaredConstructors(Class.java:2389) [:1.6.0_24] at java.lang.Class.getConstructor0(Class.java:2699) [:1.6.0_24] at java.lang.Class.getConstructor(Class.java:1657) [:1.6.0_24] at java.lang.reflect.Proxy.newProxyInstance(Proxy.java:587) [:1.6.0_24] at org.apache.cxf.tools.util.SOAPBindingUtil.getProxy(SOAPBindingUtil.java:87) [:2.3.1] at org.apache.cxf.tools.util.SOAPBindingUtil.getSoapBinding(SOAPBindingUtil.java:274) [:2.3.1] at org.apache.cxf.tools.util.SOAPBindingUtil.createSoapBinding(SOAPBindingUtil.java:426) [:2.3.1] at org.apache.cxf.binding.soap.SoapBindingFactory.createSoapBinding(SoapBindingFactory.java:213) [:2.3.1] at org.apache.cxf.binding.soap.SoapBindingFactory.createBindingInfo(SoapBindingFactory.java:198) [:2.3.1] at org.apache.cxf.binding.AbstractBindingFactory.createBindingInfo(AbstractBindingFactory.java:97) [:2.3.1] at org.apache.cxf.frontend.AbstractWSDLBasedEndpointFactory.createBindingInfo(AbstractWSDLBasedEndpointFactory.java:339) [:2.3.1] at org.apache.cxf.jaxws.JaxWsServerFactoryBean.createBindingInfo(JaxWsServerFactoryBean.java:166) [:2.3.1] at org.apache.cxf.frontend.AbstractWSDLBasedEndpointFactory.createEndpointInfo(AbstractWSDLBasedEndpointFactory.java:251) [:2.3.1] at org.apache.cxf.frontend.AbstractWSDLBasedEndpointFactory.createEndpoint(AbstractWSDLBasedEndpointFactory.java:147) [:2.3.1] at org.apache.cxf.frontend.ServerFactoryBean.create(ServerFactoryBean.java:148) [:2.3.1] at org.apache.cxf.jaxws.JaxWsServerFactoryBean.create(JaxWsServerFactoryBean.java:183) [:2.3.1] at org.apache.cxf.jaxws.EndpointImpl.getServer(EndpointImpl.java:407) [:2.3.1] at org.apache.cxf.jaxws.EndpointImpl.doPublish(EndpointImpl.java:314) [:2.3.1] at org.jboss.wsf.stack.cxf.deployment.EndpointImpl.doPublish(EndpointImpl.java:62) [:3.4.1.GA] at org.apache.cxf.jaxws.EndpointImpl.publish(EndpointImpl.java:238) [:2.3.1] at org.apache.cxf.jaxws.EndpointImpl.publish(EndpointImpl.java:481) [:2.3.1] at org.jboss.wsf.stack.cxf.configuration.NonSpringBusHolder.configure(NonSpringBusHolder.java:112) [:3.4.1.GA] at org.jboss.wsf.stack.cxf.deployment.aspect.BusDeploymentAspect.start(BusDeploymentAspect.java:110) [:3.4.1.GA] at org.jboss.webservices.integration.deployers.WSDeploymentAspectDeployer.internalDeploy(WSDeploymentAspectDeployer.java:123) [:6.0.0.Final] at org.jboss.deployers.spi.deployer.helpers.AbstractRealDeployer.deploy(AbstractRealDeployer.java:55) [:2.2.0.GA] at org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:179) [:2.2.0.GA] ... 44 more Webservice-EJB: @Stateless @WebService(name = "TestReportService", serviceName = "AsmsWebservice", targetNamespace= "http://webservice.asms.airsight.de") @SOAPBinding(style = SOAPBinding.Style.DOCUMENT, use = SOAPBinding.Use.LITERAL, parameterStyle = SOAPBinding.ParameterStyle.WRAPPED) public class TestReportService implements TestReportServiceRemote, Serializable { @PersistenceContext private EntityManager em; @WebMethod(action = "createFullTestReport") @WebResult(name="successful") public boolean createFullTestReport( @WebParam(name="name") String name, @WebParam(name="id") Long id, @WebParam(name="feedback") Boolean feedback, @WebParam(name="altitude") Double altitude) { return true; } } @Remote public interface TestReportServiceRemote { public boolean createFullTestReport(String name, Long id, Boolean feedback, Double altitude); } standard-jaxws-endpoint-config.xml: <jaxws-config xmlns="urn:jboss:jaxws-config:2.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:javaee="http://java.sun.com/xml/ns/javaee" xsi:schemaLocation="urn:jboss:jaxws-config:2.0 jaxws-config_2_0.xsd"> <endpoint-config> <config-name>Seam WebService Endpoint</config-name> <pre-handler-chains> <javaee:handler-chain> <javaee:protocol-bindings>##SOAP11_HTTP</javaee:protocol-bindings> <javaee:handler> <javaee:handler-name>SOAP Request Handler</javaee:handler-name> <javaee:handler-class>org.jboss.seam.webservice.SOAPRequestHandler</javaee:handler-class> </javaee:handler> </javaee:handler-chain> </pre-handler-chains> </endpoint-config> </jaxws-config> -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

3
6
0 / 0

[JBoss JIRA] Created: (JBAS-7909) AOPClassLoaderDeployer breaks OSGi integration

by Thomas Diesler (JIRA)

AOPClassLoaderDeployer breaks OSGi integration ---------------------------------------------- Key: JBAS-7909 URL: https://jira.jboss.org/jira/browse/JBAS-7909 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: AOP Reporter: Thomas Diesler Assignee: Kabir Khan Fix For: JBossAS-6.0.0.M3 11:11:21,726 ERROR [org.jboss.kernel.plugins.dependency.AbstractKernelController] Error installing to ClassLoader: name=vfs:///home/tdiesler/svn/jbossas/trunk/build/target/jboss-6.0.0-SNAPSHOT/server/default/deploy/osgi/org.osgi.compendium.jar state=Describe mode=Manual requiredState=ClassLoader: org.jboss.deployers.spi.DeploymentException: Error during deploy: vfs:///home/tdiesler/svn/jbossas/trunk/build/target/jboss-6.0.0-SNAPSHOT/server/default/deploy/osgi/org.osgi.compendium.jar at org.jboss.deployers.spi.DeploymentException.rethrowAsDeploymentException(DeploymentException.java:49) Caused by: java.lang.IllegalStateException: Have ClassLoaderDomain@12078a{NOT_USED_PLACEHOLDER} but no classloader domain at org.jboss.aop.asintegration.jboss5.AOPVFSClassLoaderDomainRegistry.validateInitMaps(AOPVFSClassLoaderDomainRegistry.java:85) at org.jboss.classpool.plugins.jbosscl.VFSClassLoaderDomainRegistry.initMapsForModule(VFSClassLoaderDomainRegistry.java:119) at org.jboss.classpool.plugins.jbosscl.RegisterModuleCallback.registerModule(RegisterModuleCallback.java:87) at org.jboss.classpool.plugins.jbosscl.JBossClDelegatingClassPoolFactory.create(JBossClDelegatingClassPoolFactory.java:83) at org.jboss.classpool.plugins.jbosscl.JBossClDelegatingClassPoolFactory.create(JBossClDelegatingClassPoolFactory.java:50) at org.jboss.aop.asintegration.jboss5.JBoss5Integration.create(JBoss5Integration.java:157) at org.jboss.classpool.scoped.ScopedClassPoolRepositoryImpl.createScopedClassPool(ScopedClassPoolRepositoryImpl.java:93) at org.jboss.classpool.scoped.ScopedClassPoolRepositoryImpl.registerClassLoader(ScopedClassPoolRepositoryImpl.java:125) at org.jboss.classpool.spi.ClassPoolRepository.registerClassLoader(ClassPoolRepository.java:138) at org.jboss.aop.AspectManager.registerClassLoader(AspectManager.java:846) at org.jboss.aop.asintegration.jboss5.VFSClassLoaderScopingPolicy.registerClassLoader(VFSClassLoaderScopingPolicy.java:46) at org.jboss.aop.asintegration.jboss5.AOPClassLoaderInitializer.registerLoaders(AOPClassLoaderInitializer.java:84) at org.jboss.aop.asintegration.jboss5.AOPClassLoaderInitializer.initializeForUnit(AOPClassLoaderInitializer.java:41) at org.jboss.aop.asintegration.jboss5.AOPClassLoaderDeployer.internalDeploy(AOPClassLoaderDeployer.java:65) at org.jboss.deployers.spi.deployer.helpers.AbstractRealDeployer.deploy(AbstractRealDeployer.java:55) -- 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

15 years, 2 months

4
9
0 / 0

[JBoss JIRA] Created: (JBAS-8730) Hudson testsuite hangs because of Null deploymentHash

by Thomas Diesler (JIRA)

Hudson testsuite hangs because of Null deploymentHash ------------------------------------------------------ Key: JBAS-8730 URL: https://issues.jboss.org/browse/JBAS-8730 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Thomas Diesler http://jbmuc.dyndns.org:8280/hudson/job/jbosgi-remote/6/console 09:32:34,528 INFO [org.jboss.as.server.deployment] (pool-5-thread-2) Content with name example-xservice-client-module added at location /usr/share/tomcat6/workspace/hudson-home/jobs/jbosgi-remote/workspace/jboss-7.0.0.Alpha2/standalone/data/content/00/7a37a86ec7949184af8867631ca10f61c1f7a1/content 09:32:34,612 ERROR [org.jboss.as.protocol.connection] (pool-5-thread-2) Failed to read a message: java.io.IOException: Failed to handle management operation at org.jboss.as.protocol.mgmt.AbstractMessageHandler.handleMessage(AbstractMessageHandler.java:63) at org.jboss.as.protocol.ConnectionImpl.safeHandleMessage(ConnectionImpl.java:239) at org.jboss.as.protocol.ConnectionImpl$1$1.run(ConnectionImpl.java:198) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [:1.6.0_22] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [:1.6.0_22] at java.lang.Thread.run(Thread.java:662) [:1.6.0_22] Caused by: java.lang.IllegalArgumentException: deploymentHash is null at org.jboss.as.model.ServerModelDeploymentAdd.<init>(ServerModelDeploymentAdd.java:48) at org.jboss.as.server.mgmt.deployment.ServerDeploymentManagerImpl.addServerGroupDeploymentUpdate(ServerDeploymentManagerImpl.java:302) at org.jboss.as.server.mgmt.deployment.ServerDeploymentManagerImpl.execute(ServerDeploymentManagerImpl.java:211) at org.jboss.as.server.standalone.management.ServerControllerOperationHandler$ExecuteDeploymentPlanOperation.sendResponse(ServerControllerOperationHandler.java:386) at org.jboss.as.protocol.mgmt.ManagementResponse$2.handle(ManagementResponse.java:119) at org.jboss.as.protocol.mgmt.AbstractMessageHandler.handleMessage(AbstractMessageHandler.java:59) ... 5 more -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

2
2
0 / 0

[JBoss JIRA] Created: (JBAS-8536) Cannot connect to JSR160 with IPv6

by Thomas Diesler (JIRA)

Cannot connect to JSR160 with IPv6 ---------------------------------- Key: JBAS-8536 URL: https://jira.jboss.org/browse/JBAS-8536 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Management services Reporter: Thomas Diesler Assignee: Dimitris Andreadis Fix For: 7.0.0.M2 jconsole cannot connect using a connection URL when server runs with IPv6 on Fedora13 -- 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

15 years, 2 months

2
2
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira April 2011