April 2010 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBREM-585) there is the need to add a callback listener for ssl stream invocation

by Michael Voss (JIRA)

there is the need to add a callback listener for ssl stream invocation ---------------------------------------------------------------------- Key: JBREM-585 URL: http://jira.jboss.com/jira/browse/JBREM-585 Project: JBoss Remoting Issue Type: Task Security Level: Public (Everyone can see) Components: stream Affects Versions: 2.0.0.CR1 (Boon) Reporter: Michael Voss Assigned To: Tom Elrod Fix For: 2.0.0.GA (Boon) If want to use existing ssl connector for stream invocation (using Client.invoke(InputStream,Object,Connector) ) the client has to add a callback listener to run the the invocation properly I think stream invocation should also work without the need to add a callback listener if no listener is added the following exception is thrown: by stream sender: org.jboss.remoting.ConnectionFailedException: Connection has been shutdown: javax.net.ssl.SSLProtocolException: Illegal client handshake msg, 1 at org.jboss.remoting.transport.multiplex.MultiplexClientInvoker.handleConnect(MultiplexClientInvoker.java:111) at org.jboss.remoting.MicroRemoteClientInvoker.connect(MicroRemoteClientInvoker.java:252) at org.jboss.remoting.Client.connect(Client.java:391) at org.jboss.remoting.Client.connect(Client.java:383) at org.jboss.remoting.stream.StreamHandler.<init>(StreamHandler.java:77) at org.jboss.remoting.ServerInvoker.getStreamHandler(ServerInvoker.java:1253) at org.jboss.remoting.ServerInvoker.handleInternalInvocation(ServerInvoker.java:1225) at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:983) at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:848) at org.jboss.remoting.transport.socket.ServerThread.processInvocation(ServerThread.java:447) at org.jboss.remoting.transport.socket.ServerThread.dorun(ServerThread.java:520) at org.jboss.remoting.transport.socket.ServerThread.run(ServerThread.java:257) at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:163) at org.jboss.remoting.Client.invoke(Client.java:612) at org.jboss.remoting.Client.invoke(Client.java:604) at org.jboss.remoting.Client.invoke(Client.java:1211) by stream receiver: javax.net.ssl.SSLException: Connection has been shutdown: javax.net.ssl.SSLProto colException: Illegal client handshake msg, 1 at com.sun.net.ssl.internal.ssl.SSLSocketImpl.checkEOF(Unknown Source) at com.sun.net.ssl.internal.ssl.AppInputStream.read(Unknown Source) at java.io.BufferedInputStream.fill(Unknown Source) at java.io.BufferedInputStream.read1(Unknown Source) at java.io.BufferedInputStream.read(Unknown Source) at org.jboss.remoting.transport.multiplex.InputMultiplexor$SingleGroupIn putThread.completeHeader(InputMultiplexor.java:608) at org.jboss.remoting.transport.multiplex.InputMultiplexor$SingleGroupIn putThread.doRun(InputMultiplexor.java:540) at org.jboss.remoting.transport.multiplex.utility.StoppableThread.run(St oppableThread.java:54) Caused by: javax.net.ssl.SSLProtocolException: Illegal client handshake msg, 1 at com.sun.net.ssl.internal.ssl.ClientHandshaker.processMessage(Unknown Source) at com.sun.net.ssl.internal.ssl.Handshaker.processLoop(Unknown Source) at com.sun.net.ssl.internal.ssl.Handshaker.process_record(Unknown Source ) at com.sun.net.ssl.internal.ssl.SSLSocketImpl.readRecord(Unknown Source) at com.sun.net.ssl.internal.ssl.SSLSocketImpl.performInitialHandshake(Un known Source) at com.sun.net.ssl.internal.ssl.SSLSocketImpl.writeRecord(Unknown Source ) at com.sun.net.ssl.internal.ssl.AppOutputStream.write(Unknown Source) at java.io.OutputStream.write(Unknown Source) at org.jboss.remoting.transport.multiplex.OutputMultiplexor$OutputThread .encode(OutputMultiplexor.java:580) at org.jboss.remoting.transport.multiplex.OutputMultiplexor$OutputThread .doRun(OutputMultiplexor.java:452) ... 1 more -- 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

14 years, 8 months

4
6
0 / 0

[JBoss JIRA] Created: (SECURITY-440) JBossXACML:: bug identified implementing RBAC

by Anil Saldhana (JIRA)

JBossXACML:: bug identified implementing RBAC --------------------------------------------- Key: SECURITY-440 URL: https://jira.jboss.org/jira/browse/SECURITY-440 Project: JBoss Security and Identity Management Issue Type: Bug Security Level: Public (Everyone can see) Components: JBossXACML Reporter: Anil Saldhana Assignee: Anil Saldhana -- 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, 9 months

3
2
0 / 0

[JBoss JIRA] Created: (EJBTHREE-1293) Cleanup dependencies of ejb3-core

by Carlo de Wolf (JIRA)

Cleanup dependencies of ejb3-core --------------------------------- Key: EJBTHREE-1293 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1293 Project: EJB 3.0 Issue Type: Task Components: core Reporter: Carlo de Wolf Assigned To: Carlo de Wolf Fix For: AS 5.0.0.CR1 The goal is to have ejb3-core not depend on any jboss-as artifacts. -- 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

14 years, 9 months

3
11
0 / 0

[JBoss JIRA] Created: (EJBTHREE-2057) Fix testsuite regression related to HornetQ integration

by Carlo de Wolf (JIRA)

Fix testsuite regression related to HornetQ integration ------------------------------------------------------- Key: EJBTHREE-2057 URL: https://jira.jboss.org/jira/browse/EJBTHREE-2057 Project: EJB 3.0 Issue Type: Task Reporter: Carlo de Wolf Priority: Critical Fix For: EJB3_1 1.0.6 -- 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, 9 months

3
6
0 / 0

[JBoss JIRA] Created: (EJBTHREE-1343) Remove the cyclical dependency from ejb3/core to org.jboss.jbossas-jboss-as-server

by Dimitris Andreadis (JIRA)

Remove the cyclical dependency from ejb3/core to org.jboss.jbossas-jboss-as-server ---------------------------------------------------------------------------------- Key: EJBTHREE-1343 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1343 Project: EJB 3.0 Issue Type: Task Components: core Reporter: Dimitris Andreadis Assigned To: Carlo de Wolf Priority: Critical Fix For: AS 5.0.0.CR1 ejb3/core -> jboss-as-server dependencies ------------------------------------------------------------ ejb3/core ./org/jboss/ejb3/naming/client/java/javaURLContextFactory.java depends on org.jboss.jbossas:jboss-as-server org.jboss.corba.ORBFactory ------------------------------------------------------------ ejb3/core ./org/jboss/ejb3/naming/client/java/javaURLContextFactory.java depends on org.jboss.jbossas:jboss-as-server org.jboss.naming.client.java.HandleDelegateFactory; ------------------------------------------------------------ ejb3/core ./org/jboss/ejb3/AllowedOperationsInterceptor.java ./org/jboss/ejb3/service/ServiceContainer.java ./org/jboss/ejb3/stateless/StatelessContainer.java depends on org.jboss.jbossas:jboss-as-server org.jboss.ejb.AllowedOperationsAssociation ejb3/core ./org/jboss/ejb3/mdb/MessagingContainer.java depends on org.jboss.jbossas:jboss-as-server org.jboss.jms.jndi.JMSProviderAdapter; org.jboss.jbossas:jboss-as-server ----------------------------------------- ejb3/core ./org/jboss/ejb3/timerservice/jboss/JBossTimerServiceFactory.java ./org/jboss/ejb3/timerservice/TimedObjectInvoker.java depends on org.jboss.jbossas:jboss-as-server org.jboss.ejb.txtimer.EJBTimerService; org.jboss.ejb.txtimer.TimedObjectInvoker ----------------------------------------- ejb3/core ./org/jboss/ejb3/stateful/StatefulLocalProxyFactory.java ./org/jboss/ejb3/stateless/StatelessContainer.java depends on org.jboss.jbossas:jboss-as-server org.jboss.proxy.ejb.handle.StatefulHandleImpl; org.jboss.proxy.ejb.handle.HomeHandleImpl; ------------------------------------------ ejb3/core ./org/jboss/ejb3/AllowedOperationsInterceptor.java ./org/jboss/ejb3/ContainerPlugin.java ./org/jboss/ejb3/service/ServiceContainer.java ./org/jboss/ejb3/stateless/StatelessContainer.java depends on org.jboss.jbossas:jboss-as-server org.jboss.ejb.AllowedOperationsFlags ------------------------------------------- ejb3/core ./org/jboss/ejb3/EJBProxyFactory.java depends on org.jboss.jbossas:jboss-as-server org.jboss.invocation.Invocation -------------------------------------------- ejb3/core ./org/jboss/ejb3/EJBProxyFactory.java depends on org.jboss.jbossas:jboss-as-server org.jboss.ejb.GenericEntityObjectFactory -- 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

14 years, 9 months

4
9
0 / 0

[JBoss JIRA] Created: (JGRP-726) GossipRouter: support GET and REGISTER via UDP datagram packets

by Bela Ban (JIRA)

GossipRouter: support GET and REGISTER via UDP datagram packets --------------------------------------------------------------- Key: JGRP-726 URL: http://jira.jboss.com/jira/browse/JGRP-726 Project: JGroups Issue Type: Feature Request Reporter: Bela Ban Assigned To: Vladimir Blagojevic Fix For: 2.8 Currently, GossipRouter supports only TCP. If a GossipClient calls register() or getMembers(), then a TCP connection is established and torn down after the request. This is inefficient and leads to many sockets in TIME_WAIT states (which are cleaned up after 2 * MSL seconds). If we (in GossipRouter) add an additional listener, which listens on a UDP port, and provide the same for GossipClient, we would not use precious TCP sockets. Think about: we should separate the transport in GR from the processing logic, so we could support TCP, UDP, HTTP etc. Should we use JGroups (in unicast mode) for this ? -- 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

14 years, 9 months

5
6
0 / 0

[JBoss JIRA] Created: (JGRP-763) UnicastChannelTest broken

by Bela Ban (JIRA)

UnicastChannelTest broken ------------------------- Key: JGRP-763 URL: http://jira.jboss.com/jira/browse/JGRP-763 Project: JGroups Issue Type: Bug Reporter: Bela Ban Assigned To: Bela Ban Priority: Minor Fix For: 2.8 Caused by moving the starting of threads into handleConnect() (in UDP), however, a unicast channel doesn't send down a CONNECT event. -- 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

14 years, 9 months

2
4
0 / 0

[JBoss JIRA] Created: (JGRP-705) Unicast JGroups

by Bela Ban (JIRA)

Unicast JGroups --------------- Key: JGRP-705 URL: http://jira.jboss.com/jira/browse/JGRP-705 Project: JGroups Issue Type: Feature Request Reporter: Bela Ban Assigned To: Bela Ban Fix For: 2.x Investigate use of JGroups for point-to-point communication, as a replacement for java.net{Server}Socket. E.g. Channelch=new JChannel(); ch.connect(null); // null means p2p -- 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

14 years, 9 months

2
7
0 / 0

[JBoss JIRA] Created: (JGRP-998) AUTH / FixedMembershipToken: pattern matching and match against logical names

by Bela Ban (JIRA)

AUTH / FixedMembershipToken: pattern matching and match against logical names ----------------------------------------------------------------------------- Key: JGRP-998 URL: https://jira.jboss.org/jira/browse/JGRP-998 Project: JGroups Issue Type: Feature Request Reporter: Bela Ban Assignee: Bela Ban Fix For: 2.9 #1 Use pattern matching to match hosts against senders, using regular expressions. #2 Provide matching of logical names in addition to physical addresses -- 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, 9 months

3
6
0 / 0

[JBoss JIRA] Created: (JGRP-1174) Logging: follow logging conventions

by Bela Ban (JIRA)

Logging: follow logging conventions ----------------------------------- Key: JGRP-1174 URL: https://jira.jboss.org/jira/browse/JGRP-1174 Project: JGroups Issue Type: Feature Request Reporter: Bela Ban Assignee: Bela Ban Priority: Minor Fix For: 3.0 https://docspace.corp.redhat.com/docs/DOC-30217 Requires code to be published, which can be copied over to JGroups (no JAR dep) -- 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, 9 months

4
5
0 / 0

[JBoss JIRA] Created: (JBRULES-1075) Support overloading of accumulate functions: Add int (or long) based sum's, int based avarage's, etc

by Geoffrey De Smet (JIRA)

Support overloading of accumulate functions: Add int (or long) based sum's, int based avarage's, etc ----------------------------------------------------------------------------------------------------- Key: JBRULES-1075 URL: http://jira.jboss.com/jira/browse/JBRULES-1075 Project: JBoss Rules Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Drl Parser/Builder Affects Versions: 4.0.0.GA Reporter: Geoffrey De Smet Assigned To: Edson Tirelli Priority: Minor Fix For: FUTURE TTP nl10 solver has about a 3% performance increase when switching from sumDouble to sumLong (and possibly a bit more when switching to sumInteger) There are 2 ways I see to implement this: 1) Force the user to explicitly declare he wants to use an integer based sum and add a sumInteger. This is not so user-friendly. This is what I 've done in the patch. 2) Support overloading of accumulate functions based on the function arguments. AFAIK drl is strongly typed (at least with the java dialect), so it should be theoretically possible for the drl parser to see sum($myInteger) and bind it to SumIntegerAccumulateFunction, while binding sum($myInteger.doubleValue()) to SumDoubleAccumulateFunction. And added advantage is that the drl compiler will also mark some bugs as compiler errors. For example sum($myString) -- 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

14 years, 9 months

4
5
0 / 0

[JBoss JIRA] Created: (JBBOOT-56) Add tests that bootstraps are stutdown in reverse order from start

by Andrew Lee Rubinger (JIRA)

Add tests that bootstraps are stutdown in reverse order from start ------------------------------------------------------------------ Key: JBBOOT-56 URL: https://jira.jboss.org/jira/browse/JBBOOT-56 Project: JBoss Bootstrap Issue Type: Feature Request Components: impl-base Reporter: Andrew Lee Rubinger Assignee: Andrew Lee Rubinger Fix For: 0.1.2 Ensure that we are shutting down in proper sequence. -- 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, 9 months

4
12
0 / 0

[JBoss JIRA] Created: (JGRP-798) unable to setup the protocol stack on AIX

by Aleksandar Kostadinov (JIRA)

unable to setup the protocol stack on AIX ----------------------------------------- Key: JGRP-798 URL: http://jira.jboss.com/jira/browse/JGRP-798 Project: JGroups Issue Type: Bug Affects Versions: 2.4.2 Environment: SOA-P 4.2 CP02 or EAP 4.3 CP01 AIX 5.3 IBM jdk 5.0 JGroups 2.4.2 CP01 Reporter: Aleksandar Kostadinov Assigned To: Bela Ban Starting the server produces following exception and some services fail to start properly. 2008-07-11 03:11:32,870 ERROR [org.jgroups.protocols.UDP] max_bundle_size (64000) is greater than largest TP fragmentation size (8000) 2008-07-11 03:11:32,870 ERROR [org.jgroups.protocols.UDP] the following properties are not recognized: {enable_bundling=true, max_bundle_size=64000, max_bundle_timeout=30} 2008-07-11 03:11:32,872 DEBUG [org.jboss.cache.aop.TreeCacheAop] Initialization failed jboss.cache:service=TomcatClusteringCache org.jgroups.ChannelException: unable to setup the protocol stack at org.jgroups.JChannel.init(JChannel.java:1272) at org.jgroups.JChannel.<init>(JChannel.java:265) at org.jgroups.JChannel.<init>(JChannel.java:248) at org.jboss.cache.TreeCache._createService(TreeCache.java:1474) at org.jboss.cache.TreeCache.createService(TreeCache.java:1388) at org.jboss.system.ServiceMBeanSupport.jbossInternalCreate(ServiceMBeanSupport.java:260) at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:243) at sun.reflect.GeneratedMethodAccessor6.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:618) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) at org.jboss.mx.server.Invocation.invoke(Invocation.java:86) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978) at $Proxy0.create(Unknown Source) at org.jboss.system.ServiceController.create(ServiceController.java:330) at org.jboss.system.ServiceController.create(ServiceController.java:273) at sun.reflect.GeneratedMethodAccessor4.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:618) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) at org.jboss.mx.server.Invocation.invoke(Invocation.java:86) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210) at $Proxy4.create(Unknown Source) at org.jboss.deployment.SARDeployer.create(SARDeployer.java:258) at org.jboss.deployment.MainDeployer.create(MainDeployer.java:969) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:818) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:79) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:618) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210) at $Proxy9.deploy(Unknown Source) at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanner.java:421) at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.java:634) at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.doScan(AbstractDeploymentScanner.java:263) at org.jboss.deployment.scanner.AbstractDeploymentScanner.startService(AbstractDeploymentScanner.java:336) at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289) at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:79) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:618) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) at org.jboss.mx.server.Invocation.invoke(Invocation.java:86) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978) at $Proxy0.start(Unknown Source) at org.jboss.system.ServiceController.start(ServiceController.java:417) at sun.reflect.GeneratedMethodAccessor11.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:618) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) at org.jboss.mx.server.Invocation.invoke(Invocation.java:86) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210) at $Proxy4.start(Unknown Source) at org.jboss.deployment.SARDeployer.start(SARDeployer.java:302) at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1025) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:819) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:766) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:79) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:618) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210) at $Proxy5.deploy(Unknown Source) at org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:482) at org.jboss.system.server.ServerImpl.start(ServerImpl.java:362) at org.jboss.Main.boot(Main.java:200) at org.jboss.Main$1.run(Main.java:508) at java.lang.Thread.run(Thread.java:810) Caused by: java.lang.Exception: couldn't create protocol stack at org.jgroups.stack.ProtocolStack.setup(ProtocolStack.java:182) at org.jgroups.JChannel.init(JChannel.java:1269) ... 98 more 2008-07-11 03:11:32,876 WARN [org.jboss.system.ServiceController] Problem creating service jboss.cache:service=TomcatClusteringCache org.jgroups.ChannelException: unable to setup the protocol stack at org.jgroups.JChannel.init(JChannel.java:1272) at org.jgroups.JChannel.<init>(JChannel.java:265) at org.jgroups.JChannel.<init>(JChannel.java:248) at org.jboss.cache.TreeCache._createService(TreeCache.java:1474) at org.jboss.cache.TreeCache.createService(TreeCache.java:1388) at org.jboss.system.ServiceMBeanSupport.jbossInternalCreate(ServiceMBeanSupport.java:260) at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:243) at sun.reflect.GeneratedMethodAccessor6.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:618) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) at org.jboss.mx.server.Invocation.invoke(Invocation.java:86) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978) at $Proxy0.create(Unknown Source) at org.jboss.system.ServiceController.create(ServiceController.java:330) at org.jboss.system.ServiceController.create(ServiceController.java:273) at sun.reflect.GeneratedMethodAccessor4.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:618) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) at org.jboss.mx.server.Invocation.invoke(Invocation.java:86) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210) at $Proxy4.create(Unknown Source) at org.jboss.deployment.SARDeployer.create(SARDeployer.java:258) at org.jboss.deployment.MainDeployer.create(MainDeployer.java:969) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:818) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:79) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:618) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210) at $Proxy9.deploy(Unknown Source) at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanner.java:421) at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.java:634) at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.doScan(AbstractDeploymentScanner.java:263) at org.jboss.deployment.scanner.AbstractDeploymentScanner.startService(AbstractDeploymentScanner.java:336) at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289) at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:79) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:618) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) at org.jboss.mx.server.Invocation.invoke(Invocation.java:86) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978) at $Proxy0.start(Unknown Source) at org.jboss.system.ServiceController.start(ServiceController.java:417) at sun.reflect.GeneratedMethodAccessor11.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:618) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) at org.jboss.mx.server.Invocation.invoke(Invocation.java:86) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210) at $Proxy4.start(Unknown Source) at org.jboss.deployment.SARDeployer.start(SARDeployer.java:302) at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1025) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:819) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:766) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:79) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:618) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210) at $Proxy5.deploy(Unknown Source) at org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:482) at org.jboss.system.server.ServerImpl.start(ServerImpl.java:362) at org.jboss.Main.boot(Main.java:200) at org.jboss.Main$1.run(Main.java:508) at java.lang.Thread.run(Thread.java:810) Caused by: java.lang.Exception: couldn't create protocol stack at org.jgroups.stack.ProtocolStack.setup(ProtocolStack.java:182) at org.jgroups.JChannel.init(JChannel.java:1269) ... 98 more -- 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

14 years, 9 months

3
8
0 / 0

[JBoss JIRA] Created: (JBAS-7634) Upport IIOP support for EJB 3

by Carlo de Wolf (JIRA)

Upport IIOP support for EJB 3 ----------------------------- Key: JBAS-7634 URL: https://jira.jboss.org/jira/browse/JBAS-7634 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Reporter: Carlo de Wolf Assignee: Carlo de Wolf Priority: Critical Fix For: JBossAS-6.0.0.GA -- 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, 9 months

4
6
0 / 0

[JBoss JIRA] Created: (JBLOGGING-43) Provide the ability to pull jboss-logging into a project's package space via maven

by David Lloyd (JIRA)

Provide the ability to pull jboss-logging into a project's package space via maven ---------------------------------------------------------------------------------- Key: JBLOGGING-43 URL: https://jira.jboss.org/jira/browse/JBLOGGING-43 Project: JBoss Logging Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: David Lloyd Assignee: David Lloyd Fix For: 3.0.0.Beta3-jboss-logging Via shade plugin perhaps, in order to avoid requiring an explicit dep for users on jboss-logging. -- 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, 9 months

3
8
0 / 0

[JBoss JIRA] Created: (EJBTHREE-1604) Do not create new WebServiceContext when already provided

by Alessio Soldano (JIRA)

Do not create new WebServiceContext when already provided ---------------------------------------------------------- Key: EJBTHREE-1604 URL: https://jira.jboss.org/jira/browse/EJBTHREE-1604 Project: EJB 3.0 Issue Type: Feature Request Reporter: Alessio Soldano Assignee: Alessio Soldano The StatelessContainer's method invokeEndpoint(Method method, Object[] args, InvocationContextCallback invCtxCallback) currently get the WebServiceContext instance using the right jbossws-spi factory. This is an issue with the JBossWS-Metro stack as we should use the WebServiceContext it already provides. This should be passed in as an attachment in the InvocationContextCallback. Something like this should work: ... WebServiceContext providedCtx = invCtxCallback.getAttachment(WebServiceContext.class); if (providedCtx != null) { //use the provided one through a delegate jaxwsContext = new WebServiceContextDelegate(providedCtx); } else { //do as we used to do jaxwsContext = contextFactory.newWebServiceContext(InvocationType.JAXWS_EJB3, invCtxCallback.get(javax.xml.ws.handler.MessageContext.class)); } ... This requires jbossws-spi 1.0.7 to be released and specified in the dependencies because of the WebServiceContextDelegate. -- 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, 9 months

2
1
0 / 0

[JBoss JIRA] Created: (JBEE-21) Add jboss-persistence-api_2.0_spec

by Shelly McGowan (JIRA)

Add jboss-persistence-api_2.0_spec ---------------------------------- Key: JBEE-21 URL: https://jira.jboss.org/jira/browse/JBEE-21 Project: JBoss JavaEE APIs Issue Type: Sub-task Reporter: Shelly McGowan Assignee: Shelly McGowan Fix For: 6.0.0.Alpha1 -- 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, 9 months

4
11
0 / 0

[JBoss JIRA] Created: (JBEE-19) Update jboss-ejb-api to EJB 3.1

by Carlo de Wolf (JIRA)

Update jboss-ejb-api to EJB 3.1 ------------------------------- Key: JBEE-19 URL: https://jira.jboss.org/jira/browse/JBEE-19 Project: JBoss JavaEE APIs Issue Type: Task Components: EJB API Reporter: Carlo de Wolf Assignee: Carlo de Wolf Priority: Critical -- 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, 9 months

3
5
0 / 0

[JBoss JIRA] Created: (JBBUILD-586) Rename "build" directory to "dist" in the AS build

by Paul Gier (JIRA)

Rename "build" directory to "dist" in the AS build -------------------------------------------------- Key: JBBUILD-586 URL: https://jira.jboss.org/jira/browse/JBBUILD-586 Project: JBoss Build System Issue Type: Task Components: Maven Builds Reporter: Paul Gier Assignee: Paul Gier Fix For: Maven Build Support 2010 The directory "build" should be renamed to "dist" in the AS build. Clebert suggested that this would make it more clear for new users. -- 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, 9 months

3
4
0 / 0

[JBoss JIRA] Created: (JBAS-7221) Support recovery scenarios

by Jesper Pedersen (JIRA)

Support recovery scenarios -------------------------- Key: JBAS-7221 URL: https://jira.jboss.org/jira/browse/JBAS-7221 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: ProfileService Reporter: Jesper Pedersen Assignee: Emanuel Muckenhuber Priority: Blocker Fix For: JBossAS-6.0.0.Alpha1 This is a container task for adding recovery support into the AS build. -- 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, 9 months

7
12
0 / 0

[JBoss JIRA] Created: (SECURITY-132) Traditional Authentication

by Darran Lofthouse (JIRA)

Traditional Authentication -------------------------- Key: SECURITY-132 URL: http://jira.jboss.com/jira/browse/SECURITY-132 Project: JBoss Security and Identity Management Issue Type: Task Security Level: Public (Everyone can see) Components: Negotiation Reporter: Darran Lofthouse Assigned To: Darran Lofthouse Incomming call may be traditional username / password type call but consideration needs to be given for potential outbound call. -- 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

14 years, 9 months

3
11
0 / 0

[JBoss JIRA] Created: (SECURITY-141) Fallback to different authenticator if authentication fails

by Darran Lofthouse (JIRA)

Fallback to different authenticator if authentication fails ----------------------------------------------------------- Key: SECURITY-141 URL: http://jira.jboss.com/jira/browse/SECURITY-141 Project: JBoss Security and Identity Management Issue Type: Task Security Level: Public (Everyone can see) Components: Negotiation Reporter: Darran Lofthouse Assigned To: Darran Lofthouse Need to consider how this will work especially regarding security domains, possible to do something active directory - password-stacking and an LDAP login module that for negotiation does just role mapping and for non negotiation also does authentication. -- 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

14 years, 9 months

4
11
0 / 0

[JBoss JIRA] Created: (SECURITY-45) Assimilate the Higgins Project SPI

by Anil Saldhana (JIRA)

Assimilate the Higgins Project SPI ---------------------------------- Key: SECURITY-45 URL: http://jira.jboss.com/jira/browse/SECURITY-45 Project: JBoss Security and Identity Management Issue Type: Task Security Level: Public (Everyone can see) Components: Security SPI Reporter: Anil Saldhana Assigned To: Anil Saldhana Fix For: 2.0.1 There is a need to get the SPI for Project Higgins Trust Framework into the JBoss Security SPI. -- 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

14 years, 9 months

2
5
0 / 0

[JBoss JIRA] Created: (SECURITY-470) Callbackhandlers to get information from LDAP

by Anil Saldhana (JIRA)

Callbackhandlers to get information from LDAP --------------------------------------------- Key: SECURITY-470 URL: https://jira.jboss.org/jira/browse/SECURITY-470 Project: PicketBox (JBoss Security and Identity Management) Issue Type: Feature Request Security Level: Public (Everyone can see) Components: PicketBox Reporter: Anil Saldhana Assignee: Anil Saldhana Fix For: PicketBox_v3_0_beta4 -- 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, 9 months

3
3
0 / 0

[JBoss JIRA] Created: (JGRP-790) FD_SOCK / shared transport: make FD_SOCK a singleton

by Bela Ban (JIRA)

FD_SOCK / shared transport: make FD_SOCK a singleton ---------------------------------------------------- Key: JGRP-790 URL: http://jira.jboss.com/jira/browse/JGRP-790 Project: JGroups Issue Type: Feature Request Reporter: Bela Ban Assigned To: Bela Ban Fix For: 2.7 If we have multiple channels over the same shared transport, FD_SOCK creates multiple server sockets within the same JVM. Investigate whether we can collapse those into one server socket if we run over the same shared transport. -- 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

14 years, 9 months

2
3
0 / 0

[JBoss JIRA] Created: (JBAS-6332) Injection from outside modules

by Carlo de Wolf (JIRA)

Injection from outside modules ------------------------------ Key: JBAS-6332 URL: https://jira.jboss.org/jira/browse/JBAS-6332 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: JBossAS-5.0.0.GA Reporter: Carlo de Wolf When a servlet is packaged standalone (outside ear) and an EJB is packaged standalone, the EJB can't be injected into the servlet without specifying a JNDI name somewhere. It would be nice to have the ability to inject beans from outside your own enterprise application. -- 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, 9 months

7
9
0 / 0

[JBoss JIRA] Created: (SECURITY-467) Callbackhandlers to get information from various sources (DB/LDAP)

by Anil Saldhana (JIRA)

Callbackhandlers to get information from various sources (DB/LDAP) ------------------------------------------------------------------ Key: SECURITY-467 URL: https://jira.jboss.org/jira/browse/SECURITY-467 Project: PicketBox (JBoss Security and Identity Management) Issue Type: Feature Request Security Level: Public (Everyone can see) Components: PicketBox Reporter: Anil Saldhana Assignee: Anil Saldhana Fix For: PicketBox_v3_0_beta2 -- 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, 9 months

6
9
0 / 0

[JBoss JIRA] Created: (JBAS-7656) jboss_init_redhat.sh needs to be more robust

by Henrik Aronsen (JIRA)

jboss_init_redhat.sh needs to be more robust -------------------------------------------- Key: JBAS-7656 URL: https://jira.jboss.org/jira/browse/JBAS-7656 Project: JBoss Application Server Issue Type: Patch Security Level: Public (Everyone can see) Components: Other Reporter: Henrik Aronsen Fix For: JBossAS-6.0.0.M2, JBossAS-6.0.0.M3, JBossAS-6.0.0.CR1, JBossAS-6.0.0.GA I have tried to address the shortcomings of the current JBoss init script for RHEL5: - Uses PID file - Supports chkconfig - Supports start, stop, force-stop, reload, force-reload, status - Supports custom user and password on shutdown - Supports custom jndi host/port on shutdown - Does not allow second instance to start when one is already running - Does not rely on other files such as run.sh and run.conf - Verifies successful startup - The init script does not have to be edited, use the standard location for configuration (/etc/default/jboss) instead - Runs out of the box when no configuration is provided - Should support most Linuces All feedback is welcome -- I'm sure I forgot something in the provided script The init script is currently maintained at http://code.google.com/p/jboss-rpm/source/browse/#svn/trunk/src/main/etc (This issue was copied from JBPAPP-3194 as suggested by Fernando Nasser) -- 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, 9 months

3
7
0 / 0

[JBoss JIRA] Created: (JBEE-45) Release JACC 1.1 APIs built with JDK 1.4

by Shelly McGowan (JIRA)

Release JACC 1.1 APIs built with JDK 1.4 ---------------------------------------- Key: JBEE-45 URL: https://jira.jboss.org/jira/browse/JBEE-45 Project: JBoss JavaEE APIs Issue Type: Bug Reporter: Shelly McGowan Assignee: Shelly McGowan Fix For: 1.0.0.CR1 To replace this: http://repository.jboss.org/maven2/org/jboss/javaee/jboss-jacc-api_JDK4/1... which contains a servlet snapshot Needed by Hibernate -- 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, 9 months

2
2
0 / 0

[JBoss JIRA] Created: (SECURITY-216) Technical White Paper on SSL usage with JBoss

by Anil Saldhana (JIRA)

Technical White Paper on SSL usage with JBoss --------------------------------------------- Key: SECURITY-216 URL: http://jira.jboss.com/jira/browse/SECURITY-216 Project: JBoss Security and Identity Management Issue Type: Feature Request Security Level: Public (Everyone can see) Components: White Papers Reporter: Anil Saldhana Assigned To: Marcus Moyses Fix For: 2.0.2.GA This is one of the most critical white papers of a lot of value for JBoss users, JBoss customers as well as JBoss Support. Reference: http://wiki.jboss.org/wiki/SSLSetup Things to include: 1) Keytool examples 2) Generate CSR 3) Import Cert Chains 4) Tomcat configuration 5) RMISSL Server socket factories etc.... -- 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

14 years, 9 months

2
2
0 / 0

[JBoss JIRA] Created: (SECURITY-345) Create test case for decryption of password with leading zero for SecureIdentityLoginModule

by Marcus Moyses (JIRA)

Create test case for decryption of password with leading zero for SecureIdentityLoginModule ------------------------------------------------------------------------------------------- Key: SECURITY-345 URL: https://jira.jboss.org/jira/browse/SECURITY-345 Project: JBoss Security and Identity Management Issue Type: Sub-task Security Level: Public (Everyone can see) Components: JBossSX Affects Versions: 2.0.2.SP3 Reporter: Marcus Moyses Assignee: Marcus Moyses An example of password that would lead to an error in the decryption process is dynamcusr. Create a test case for this to guarantee the error is gone. -- 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, 9 months

3
2
0 / 0

[JBoss JIRA] Created: (EJBTHREE-1939) Enhance the plugin to allow EJB 3.1 features to be plugged into the AS

by jaikiran pai (JIRA)

Enhance the plugin to allow EJB 3.1 features to be plugged into the AS ---------------------------------------------------------------------- Key: EJBTHREE-1939 URL: https://jira.jboss.org/jira/browse/EJBTHREE-1939 Project: EJB 3.0 Issue Type: Task Components: installer, plugin Affects Versions: EJB 3.1 Reporter: jaikiran pai Assignee: jaikiran pai EJB 3.1 features are targeted for AS 6. However, some of the features can be made available through the EJB3 plugin against AS 5 (after AS 5.2 Beta is released). The objectives of this task is to: 1) Allow users to opt for the regular EJB3 bug fixes that come in from the current EJB3 plugin against AS-5 2) Allow users to opt for EJB 3.1 features through the plugin against AS-5 -- 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, 9 months

2
1
0 / 0

[JBoss JIRA] Created: (EJBTHREE-1752) Unable to create annotation for method/field create for EJB

by Eugene Torkhov (JIRA)

Unable to create annotation for method/field create for EJB ----------------------------------------------------------- Key: EJBTHREE-1752 URL: https://jira.jboss.org/jira/browse/EJBTHREE-1752 Project: EJB 3.0 Issue Type: Bug Components: ejb3 Affects Versions: AS 4.2.3.GA, AS 5.0.0.CR1 Environment: AS 5.0.0.GA Windows Reporter: Eugene Torkhov Priority: Blocker Attachments: authmanager.jar like EJBTHREE-1149 org.jboss.deployers.spi.DeploymentException: Error deploying authmanager.jar: Unable to create annotation for method/field create for EJB com.nt.workstation.security.Authentication at org.jboss.ejb3.deployers.Ejb3Deployer.deploy(Ejb3Deployer.java:203) at org.jboss.ejb3.deployers.Ejb3Deployer.deploy(Ejb3Deployer.java:104) 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.install(DeployersImpl.java:1098) at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:348) at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1598) at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:934) at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1062) 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:545) at org.jboss.system.server.profileservice.ProfileServiceBootstrap.loadProfile(ProfileServiceBootstrap.java:304) at org.jboss.system.server.profileservice.ProfileServiceBootstrap.start(ProfileServiceBootstrap.java:205) at org.jboss.bootstrap.AbstractServerImpl.start(AbstractServerImpl.java:405) at org.jboss.Main.boot(Main.java:209) at org.jboss.Main$1.run(Main.java:547) at java.lang.Thread.run(Unknown Source) Caused by: java.lang.RuntimeException: Unable to create annotation for method/field create for EJB com.nt.workstation.security.Authentication at org.jboss.ejb3.Ejb3DescriptorHandler.addAnnotations(Ejb3DescriptorHandler.java:2214) at org.jboss.ejb3.Ejb3DescriptorHandler.addAnnotations(Ejb3DescriptorHandler.java:2227) at org.jboss.ejb3.Ejb3DescriptorHandler.addSecurityAnnotations(Ejb3DescriptorHandler.java:1092) at org.jboss.ejb3.Ejb3DescriptorHandler.addDescriptorAnnotations(Ejb3DescriptorHandler.java:919) at org.jboss.ejb3.Ejb3DescriptorHandler.addDescriptorAnnotations(Ejb3DescriptorHandler.java:898) at org.jboss.ejb3.Ejb3DescriptorHandler.getStatelessContainer(Ejb3DescriptorHandler.java:513) at org.jboss.ejb3.Ejb3AnnotationHandler.getContainers(Ejb3AnnotationHandler.java:203) at org.jboss.ejb3.Ejb3Deployment.deployElement(Ejb3Deployment.java:668) at org.jboss.ejb3.Ejb3Deployment.deployElement(Ejb3Deployment.java:628) at org.jboss.ejb3.Ejb3Deployment.deployUrl(Ejb3Deployment.java:610) at org.jboss.ejb3.Ejb3Deployment.deploy(Ejb3Deployment.java:573) at org.jboss.ejb3.Ejb3Deployment.create(Ejb3Deployment.java:488) at org.jboss.ejb3.deployers.Ejb3Deployer.deploy(Ejb3Deployer.java:189) ... 22 more Caused by: java.lang.NoSuchFieldException: create at java.lang.Class.getDeclaredField(Unknown Source) at org.jboss.ejb3.Ejb3DescriptorHandler.addAnnotations(Ejb3DescriptorHandler.java:2166) ... 34 more -- 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, 9 months

5
10
0 / 0

[JBoss JIRA] Created: (JGRP-1100) ENCRYPT debug log prints "hex" output in ambiguous format

by Dennis Reed (JIRA)

ENCRYPT debug log prints "hex" output in ambiguous format --------------------------------------------------------- Key: JGRP-1100 URL: https://jira.jboss.org/jira/browse/JGRP-1100 Project: JGroups Issue Type: Bug Affects Versions: 2.4.7 Reporter: Dennis Reed Assignee: Dennis Reed ENCRYPT.formatArray doesn't convert a byte array straight to hex. It leaves off any leading 0 in a byte and appends ffffff in front of any negative byte. This prevents the original data from easily being reconstructed from the log for debugging purposes. -- 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, 10 months

4
12
0 / 0

[JBoss JIRA] Created: (JBRULES-2409) Quotes should not be escaped when parsing a decision table

by Jos Hendriks (JIRA)

Quotes should not be escaped when parsing a decision table ---------------------------------------------------------- Key: JBRULES-2409 URL: https://jira.jboss.org/jira/browse/JBRULES-2409 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-decisiontables Affects Versions: 5.0.1.FINAL Environment: jdk 1.6 update 12 windows XP Reporter: Jos Hendriks Assignee: Mark Proctor Since drools 5 quotes that are in an action cell of a decision table are escaped. As we are using method calls with String parameters in our action cells this results in invalid drl. I've reproduced the issue in the example decision table project generated by the eclipse plugin. After generating a new Drools project with decision table example I added the following to the Message class: public String getMessage(String dummy) { return this.message; } In the decision table I change cell E9 from 'm.setMessage("$param");update(m);' to 'm.setMessage($param);update(m);' and cell E11 from 'Goodbye cruel world' to 'm.getMessage("msg")'. When I use Drools 5 I get escaped double-quotes which causes an error in com.sample.DecisionTableTest.readKnowledgeBase: m.setMessage(m.getMessage(\"msg\"));update(m); Version 4.0.7 did not escape quotes and correctly generated the drl: m.setMessage(m.getMessage("msg"));update(m); I found out that escaping of quoted has been added by request, JBRULES-1811. Please reconsider the decision and or implementation made to solve that issue. Possibly add a keyword to the decision table to define the way qoutes are parsed? Like Sequential for salience.... The forum entry I have made includes the files and full drl. Please contact me if you need more information or help. -- 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, 10 months

7
17
0 / 0

[JBoss JIRA] Created: (JBRULES-2222) Rule silently discarded if RHS calls an undefined DRL function

by Wolfgang Laun (JIRA)

Rule silently discarded if RHS calls an undefined DRL function -------------------------------------------------------------- Key: JBRULES-2222 URL: https://jira.jboss.org/jira/browse/JBRULES-2222 Project: JBoss Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-compiler Affects Versions: 5.0.1.FINAL Reporter: Wolfgang Laun Assignee: Mark Proctor If a function bar is called on a RHS of a rule in the same .drl file without being defined in the same .drl file, the .drl is compiled without kBuilder.getErrors() returning an error, and the rule is silently discarded (not firing, although it should). - Note that this error occurred when there was a function bar defined in another .drl file of the same package. Eclipse does indicate an error. -- 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, 10 months

2
1
0 / 0

[JBoss JIRA] Created: (JBRULES-1923) Rule order counts when adding inheriting rules

by Toni Rikkola (JIRA)

Rule order counts when adding inheriting rules ---------------------------------------------- Key: JBRULES-1923 URL: https://jira.jboss.org/jira/browse/JBRULES-1923 Project: JBoss Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-compiler Affects Versions: FUTURE Reporter: Toni Rikkola Assignee: Mark Proctor When inheriting rules, the order they are written to DRL counts. dward noticed this when using Guvnor. There is no way to control the order of the rules in Guvnor, so because of this inheritance doesn't always work. This works: rule A when ... then end rule B extends A when ... then end This doesn't work: rule B extends A when ... then end rule A when ... then end -- 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, 10 months

5
11
0 / 0

[JBoss JIRA] Created: (SECURITY-74) Policy Management Console using JBoss SEAM

by Anil Saldhana (JIRA)

Policy Management Console using JBoss SEAM ------------------------------------------ Key: SECURITY-74 URL: http://jira.jboss.com/jira/browse/SECURITY-74 Project: JBoss Security and Identity Management Issue Type: Feature Request Security Level: Public (Everyone can see) Components: JBossXACML-Console Reporter: Anil Saldhana Assigned To: Anil Saldhana Fix For: 2.0.1 Need for a progressive Policy Management console using JBoss SEAM. The JAXB2 object model provided with JBoss XACML can be used to construct the policies. -- 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

14 years, 10 months

2
4
0 / 0

[JBoss JIRA] Created: (JGRP-693) Incorporate MultithreadedTestCase (MTC) usage into JGroups testsuite

by Richard Achmatowicz (JIRA)

Incorporate MultithreadedTestCase (MTC) usage into JGroups testsuite -------------------------------------------------------------------- Key: JGRP-693 URL: http://jira.jboss.com/jira/browse/JGRP-693 Project: JGroups Issue Type: Task Environment: JGroups testsuite test cases Reporter: Richard Achmatowicz Assigned To: Bela Ban Fix For: 2.7 MultithreadedTestCase (MTC) is an open-source testing framework which supports the writing of multithreaded test cases. It introduces a global tick-counter which provides a deterministic form of thread synchronization, based on the number of times all threads in a test case are blocked. The tool works well ina debugger, unlike other approximate forms of synchronization (e.g. sleep()) This issue concerns using MTC in order to simplify and improve test cases in the JGroups test suite in which concurrency and blocking are at issue. -- 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

14 years, 10 months

2
2
0 / 0

[JBoss JIRA] Created: (JBRULES-1778) Drools builder raises errors for non-decision tables XLS files

by Edson Tirelli (JIRA)

Drools builder raises errors for non-decision tables XLS files -------------------------------------------------------------- Key: JBRULES-1778 URL: https://jira.jboss.org/jira/browse/JBRULES-1778 Project: JBoss Drools Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 5.0.0.M1 Reporter: Edson Tirelli Assignee: Kris Verlaenen Fix For: FUTURE As it is now, the eclipse "drools builder" is raising errors for any XLS file that is not a decision table. For instance, in drools-examples there is the ExampleCheese.xls file used for a drools-template example that acuses the following error: No RuleTable's were found in spreadsheet. ExampleCheese.xls drools-examples/src/main/rules/org/drools/examples Unknown Drools Error -- 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, 10 months

4
3
0 / 0

[JBoss JIRA] Created: (JBRULES-2284) OutOfMemoryException at DT loading

by Sergey Vanskov (JIRA)

OutOfMemoryException at DT loading ---------------------------------- Key: JBRULES-2284 URL: https://jira.jboss.org/jira/browse/JBRULES-2284 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-decisiontables Affects Versions: 5.0.1.FINAL Environment: Core2Quad Windows XP Pro 64 Reporter: Sergey Vanskov Assignee: Mark Proctor I have created DT having 20.000 rows with 4 conditions and 1 action in CSV format and set the following parameters for JVM -Xmx3072M -XX:MaxPermSize=256M. I haveOutOfMemoryException with the following stack trace java.lang.OutOfMemoryError: Java heap space at java.lang.String.format(String.java:2558) at org.drools.lang.DroolsParserExceptionFactory.formatParserLocation(DroolsParserExceptionFactory.java:203) at org.drools.lang.DroolsParserExceptionFactory.createErrorMessage(DroolsParserExceptionFactory.java:104) at org.drools.lang.DroolsParserExceptionFactory.createDroolsException(DroolsParserExceptionFactory.java:89) at org.drools.lang.DRLParser.reportError(DRLParser.java:350) at org.antlr.runtime.BaseRecognizer.recoverFromMismatchedToken(BaseRecognizer.java:624) at org.antlr.runtime.BaseRecognizer.match(BaseRecognizer.java:115) at org.drools.lang.DRLParser.fact(DRLParser.java:9841) at org.drools.lang.DRLParser.lhs_pattern(DRLParser.java:9388) at org.drools.lang.DRLParser.pattern_source(DRLParser.java:7432) at org.drools.lang.DRLParser.lhs_unary(DRLParser.java:6582) at org.drools.lang.DRLParser.lhs_and(DRLParser.java:6229) at org.drools.lang.DRLParser.lhs_or(DRLParser.java:5877) at org.drools.lang.DRLParser.lhs(DRLParser.java:5673) at org.drools.lang.DRLParser.normal_lhs_block(DRLParser.java:5580) at org.drools.lang.DRLParser.when_part(DRLParser.java:3975) at org.drools.lang.DRLParser.rule(DRLParser.java:3769) at org.drools.lang.DRLParser.statement(DRLParser.java:993) at org.drools.lang.DRLParser.compilation_unit(DRLParser.java:484) at org.drools.compiler.DrlParser.compile(DrlParser.java:238) at org.drools.compiler.DrlParser.parse(DrlParser.java:78) at org.drools.compiler.DrlParser.parse(DrlParser.java:83) at org.drools.compiler.PackageBuilder.addPackageFromDrl(PackageBuilder.java:275) at org.drools.compiler.PackageBuilder.addKnowledgeResource(PackageBuilder.java:510) at org.drools.builder.impl.KnowledgeBuilderImpl.add(KnowledgeBuilderImpl.java:31) .... Is 3Gb not enough for such a problem?! How may memory requirements be estimated? -- 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, 10 months

4
5
0 / 0

[JBoss JIRA] Created: (JBRULES-2297) Enable marshalling of events in drools fusion

by Maciej Prochniak (JIRA)

Enable marshalling of events in drools fusion --------------------------------------------- Key: JBRULES-2297 URL: https://jira.jboss.org/jira/browse/JBRULES-2297 Project: Drools Issue Type: Feature Request Security Level: Public (Everyone can see) Components: drools-core, drools-core (fusion) Affects Versions: 5.1.0.M1 Reporter: Maciej Prochniak Assignee: Mark Proctor Currently, when one tries to (un)marshall EventFactHandle an exception is thrown, as default marshaller recognizes only DefaultFactHandle. -- 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

3
8
0 / 0

[JBoss JIRA] Created: (JBBOOT-116) Implement a Graceful Shutdown API and Implementation

by Andrew Lee Rubinger (JIRA)

Implement a Graceful Shutdown API and Implementation ----------------------------------------------------- Key: JBBOOT-116 URL: https://jira.jboss.org/jira/browse/JBBOOT-116 Project: JBoss Bootstrap Issue Type: Feature Request Reporter: Andrew Lee Rubinger Assignee: Andrew Lee Rubinger As identified by the Summer 2009 AS Meeting. Requirements: * Decoupled sufficiently from other Bootstrap mechanisms as to not leak out dependencies * 2-phase event-listener registration API * May be injected into MC Beans * 1st phase is a concurrent broadcast to all subsystems which have registered: "prepare for shutdown" * When all listeners have reported "ready", fire 2nd phase: "shutdown" -- 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

3
4
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-1462) Message expiration is not correctly managed

by Ivan (JIRA)

Message expiration is not correctly managed ------------------------------------------- Key: JBMESSAGING-1462 URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1462 Project: JBoss Messaging Issue Type: Bug Components: Messaging Core Affects Versions: 1.4.1.GA Environment: JBAS 5.0GA, JBM 1.4.1GA, persistence on Oracle 10i Reporter: Ivan Assignee: Tim Fox 1) A topic is created 2) A durable subscriber is created fro the topic 3) A message is sent on the topic 4) The durable subscriber pulls the message from the topic ( receive() ) but don't ack 5) The durable subscriber is closed, subscriber session.unsuscribe(name) is called but an exception is thrown and then the subsciber session is closed. As result of this a message, expired, with DELIVERY_COUNT = 1 will remain on the database forever. -- 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

4
20
0 / 0

[JBoss JIRA] Created: (JBRULES-1287) Use of reserved word as bound variable in a pattern results as NPE

by Justin Wick (JIRA)

Use of reserved word as bound variable in a pattern results as NPE ------------------------------------------------------------------ Key: JBRULES-1287 URL: http://jira.jboss.com/jira/browse/JBRULES-1287 Project: JBoss Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: Drl Parser/Builder, Eclipse IDE Affects Versions: 4.0.2 Environment: Eclipse 3.2, Windows XP Reporter: Justin Wick Assigned To: Mark Proctor example: rule "This generates an NPE" when result : ReservedWordNPEFact(data < 15) then result.setData(new Integer(1)); end At least in the eclipse IDE, this generates an NPE. Change result to something like: rule "This generates an NPE" when f: ReservedWordNPEFact(data < 15) then f.setData(new Integer(1)); end and it goes away. -- 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

14 years, 11 months

5
11
0 / 0

[JBoss JIRA] Created: (JBRULES-552) Outline problems in DRL editor

by Dirk Bergstrom (JIRA)

Outline problems in DRL editor ------------------------------ Key: JBRULES-552 URL: http://jira.jboss.com/jira/browse/JBRULES-552 Project: JBoss Rules Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 3.0.4 Reporter: Dirk Bergstrom Assigned To: Mark Proctor Priority: Minor Two (possibly related) problems with the outline view in the DRL editor: *) Rules that are commented out via a multi-line comment (/* ... */) still appear in the outline. *) Clicking on the name of a rule highlights some text near that rule. I assume it's supposed to highight the title of the rule, but it misses. Same thing affects the imports. -- 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

14 years, 11 months

4
5
0 / 0

[JBoss JIRA] Created: (JGRP-696) Incorporate RedHat clustering documentation into JGroups manual

by Richard Achmatowicz (JIRA)

Incorporate RedHat clustering documentation into JGroups manual --------------------------------------------------------------- Key: JGRP-696 URL: http://jira.jboss.com/jira/browse/JGRP-696 Project: JGroups Issue Type: Sub-task Reporter: Richard Achmatowicz Assigned To: Bela Ban Fix For: 2.x Incorporate relevant sections into the manual. -- 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

14 years, 11 months

2
1
0 / 0

[JBoss JIRA] Created: (JGRP-698) Incorporate wiki documentation into the manual

by Richard Achmatowicz (JIRA)

Incorporate wiki documentation into the manual ---------------------------------------------- Key: JGRP-698 URL: http://jira.jboss.com/jira/browse/JGRP-698 Project: JGroups Issue Type: Sub-task Reporter: Richard Achmatowicz Assigned To: Bela Ban Fix For: 2.x The JGroups wiki contains a lot of up-to-the-minute information on JGroups protocols, configuration and other aspects. Incorporate relevant elements into the manual to improve content and scope. -- 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

14 years, 11 months

2
1
0 / 0

[JBoss JIRA] Created: (JGRP-695) Consolidate and improve on JGroups documentation

by Richard Achmatowicz (JIRA)

Consolidate and improve on JGroups documentation ------------------------------------------------- Key: JGRP-695 URL: http://jira.jboss.com/jira/browse/JGRP-695 Project: JGroups Issue Type: Task Reporter: Richard Achmatowicz Assigned To: Bela Ban Fix For: 2.x Consolidate and improve on JGroups documentation, aiming at a comprehensive and complete manual to be included with the distribution. There are a number of existing sources of documentation which have not yet been incorporated into the manual - RedHat documentation on clustering, existing articlesand wiki pages - and these should be consolidated into the manual for the benefit of users. -- 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

14 years, 11 months

2
1
0 / 0

[JBoss JIRA] Created: (JBRULES-2230) DecisionTable added to KnowledgeAgent via change-set throws a NullPointerException

by Steve Ronderos (JIRA)

DecisionTable added to KnowledgeAgent via change-set throws a NullPointerException ---------------------------------------------------------------------------------- Key: JBRULES-2230 URL: https://jira.jboss.org/jira/browse/JBRULES-2230 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-compiler, drools-core Affects Versions: 5.0.1.FINAL Environment: Windows XP Java 1.5 Reporter: Steve Ronderos Assignee: Mark Proctor When adding a change-set which contains a decision table to a KnowledgeAgent I receive the following error: Exception in thread "main" java.lang.NullPointerException at org.drools.decisiontable.DecisionTableProviderImpl.compileStream(DecisionTableProviderImpl.java:26) at org.drools.decisiontable.DecisionTableProviderImpl.loadFromInputStream(DecisionTableProviderImpl.java:19) at org.drools.compiler.DecisionTableFactory.loadFromInputStream(DecisionTableFactory.java:16) at org.drools.compiler.PackageBuilder.addKnowledgeResource(PackageBuilder.java:508) at org.drools.builder.impl.KnowledgeBuilderImpl.add(KnowledgeBuilderImpl.java:25) at org.drools.agent.impl.KnowledgeAgentImpl.rebuildResources(KnowledgeAgentImpl.java:386) at org.drools.agent.impl.KnowledgeAgentImpl.applyChangeSet(KnowledgeAgentImpl.java:120) at org.drools.agent.impl.KnowledgeAgentImpl.applyChangeSet(KnowledgeAgentImpl.java:109) at org.drools.bug.AgentDecisionTableBug.main(AgentDecisionTableBug.java:12) I tested with 5.0.1 and 5.1.0.SNAPSHOT. I looked into the code a little and it appears that KnowledgeAgentImpl.rebuildResources does not parse the DecisionTable's configuration and pass it to the overloaded KnowledgeBuilderImpl.add method. -- 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

7
11
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 2010