[JBoss JIRA] (WFLY-3913) HTTPS socket-binding definition always needed
by Tomaz Cerar (JIRA)
[ https://issues.jboss.org/browse/WFLY-3913?page=com.atlassian.jira.plugin.... ]
Tomaz Cerar reassigned WFLY-3913:
---------------------------------
Assignee: Tomaz Cerar (was: Jason Greene)
> HTTPS socket-binding definition always needed
> ---------------------------------------------
>
> Key: WFLY-3913
> URL: https://issues.jboss.org/browse/WFLY-3913
> Project: WildFly
> Issue Type: Bug
> Components: Web (Undertow)
> Affects Versions: 8.1.0.Final
> Reporter: Jose Monreal
> Assignee: Tomaz Cerar
> Labels: https, standalone
>
> When removing HTTPS socket-binding from the standalone.xml file, the server start's in errors.
> The errors are the following:
> 13:55:32,002 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) JBAS014613: Operation ("add") failed - address: ([
> ("subsystem" => "undertow"),
> ("server" => "default-server"),
> ("http-listener" => "default")
> ]) - failure description: {"JBAS014771: Services with missing/unavailable dependencies" => ["jboss.undertow.listener.default is missing [jboss.binding.https]"]}
> 13:55:32,005 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) JBAS014613: Operation ("add") failed - address: ([("subsystem" => "webservices")]) - failure description: {"JBAS014879: One or more services were unable to start due to one or more indirect dependencies not being available." => {
> "Services that were unable to start:" => ["jboss.ws.config"],
> "Services that may be the cause:" => [
> "jboss.binding.https",
> "jboss.remoting.remotingConnectorInfoService.http-remoting-connector"
> ]
> }}
> 13:55:32,007 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) JBAS014613: Operation ("add") failed - address: ([
> ("subsystem" => "ejb3"),
> ("service" => "remote")
> ]) - failure description: {"JBAS014771: Services with missing/unavailable dependencies" => ["jboss.ejb3.connector is missing [jboss.remoting.remotingConnectorInfoService.http-remoting-connector]"]}
> 13:55:32,074 INFO [org.jboss.as.controller] (Controller Boot Thread) JBAS014774: Service status report
> JBAS014775: New missing/unsatisfied dependencies:
> service jboss.binding.https (missing) dependents: [service jboss.undertow.listener.default]
> service jboss.remoting.remotingConnectorInfoService.http-remoting-connector (missing) dependents: [service jboss.ejb3.connector]
>
> 13:55:32,085 ERROR [org.jboss.as] (Controller Boot Thread) JBAS015875: WildFly 8.1.0.Final "Kenny" started (with errors) in 3475ms - Started 197 of 252 services (3 services failed or missing dependencies, 78 services are lazy, passive or on-demand
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
9 years, 9 months
[JBoss JIRA] (WFLY-3913) HTTPS socket-binding definition always needed
by Jose Monreal (JIRA)
Jose Monreal created WFLY-3913:
----------------------------------
Summary: HTTPS socket-binding definition always needed
Key: WFLY-3913
URL: https://issues.jboss.org/browse/WFLY-3913
Project: WildFly
Issue Type: Bug
Affects Versions: 8.1.0.Final
Reporter: Jose Monreal
Assignee: Jason Greene
When removing HTTPS socket-binding from the standalone.xml file, the server start's in errors.
The errors are the following:
13:55:32,002 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) JBAS014613: Operation ("add") failed - address: ([
("subsystem" => "undertow"),
("server" => "default-server"),
("http-listener" => "default")
]) - failure description: {"JBAS014771: Services with missing/unavailable dependencies" => ["jboss.undertow.listener.default is missing [jboss.binding.https]"]}
13:55:32,005 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) JBAS014613: Operation ("add") failed - address: ([("subsystem" => "webservices")]) - failure description: {"JBAS014879: One or more services were unable to start due to one or more indirect dependencies not being available." => {
"Services that were unable to start:" => ["jboss.ws.config"],
"Services that may be the cause:" => [
"jboss.binding.https",
"jboss.remoting.remotingConnectorInfoService.http-remoting-connector"
]
}}
13:55:32,007 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) JBAS014613: Operation ("add") failed - address: ([
("subsystem" => "ejb3"),
("service" => "remote")
]) - failure description: {"JBAS014771: Services with missing/unavailable dependencies" => ["jboss.ejb3.connector is missing [jboss.remoting.remotingConnectorInfoService.http-remoting-connector]"]}
13:55:32,074 INFO [org.jboss.as.controller] (Controller Boot Thread) JBAS014774: Service status report
JBAS014775: New missing/unsatisfied dependencies:
service jboss.binding.https (missing) dependents: [service jboss.undertow.listener.default]
service jboss.remoting.remotingConnectorInfoService.http-remoting-connector (missing) dependents: [service jboss.ejb3.connector]
13:55:32,085 ERROR [org.jboss.as] (Controller Boot Thread) JBAS015875: WildFly 8.1.0.Final "Kenny" started (with errors) in 3475ms - Started 197 of 252 services (3 services failed or missing dependencies, 78 services are lazy, passive or on-demand
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
9 years, 9 months
[JBoss JIRA] (WFCORE-131) Upgrade JBoss VFS
by David Lloyd (JIRA)
David Lloyd created WFCORE-131:
----------------------------------
Summary: Upgrade JBoss VFS
Key: WFCORE-131
URL: https://issues.jboss.org/browse/WFCORE-131
Project: WildFly Core
Issue Type: Component Upgrade
Components: VFS
Reporter: David Lloyd
Assignee: Tomaz Cerar
Fix For: 1.0.0.CR1
Upgrade VFS to a version which includes a fix for JBVFS-197.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
9 years, 9 months
[JBoss JIRA] (JBVFS-197) VFSUtils#getVirtualURL requires permissions
by David Lloyd (JIRA)
David Lloyd created JBVFS-197:
---------------------------------
Summary: VFSUtils#getVirtualURL requires permissions
Key: JBVFS-197
URL: https://issues.jboss.org/browse/JBVFS-197
Project: JBoss VFS
Issue Type: Bug
Affects Versions: 3.2.6.Final
Reporter: David Lloyd
Assignee: Tomaz Cerar
The {{org.jboss.vfs.VFSUtils#getVirtualURL(VirtualFile)}} method requires the permission {{java.net.NetPermission" specifyStreamHandler"}}. Therefore the URL construction should be in a privileged block.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
9 years, 9 months
[JBoss JIRA] (DROOLS-604) Problems in code generation and parsing when a method is called from Guided Rules Editor
by Abel Marrero Santos (JIRA)
[ https://issues.jboss.org/browse/DROOLS-604?page=com.atlassian.jira.plugin... ]
Abel Marrero Santos updated DROOLS-604:
---------------------------------------
Description:
I have found a problem in code generation when we use the feature "call a method on <variable>" from the Guided Rule Editor. An InvocationTargetException caused by a ClassCastException is thrown in RuleModelDRLPersistenceImpl.generateSetMethodCallsMethod method.
I have found other issues that I think are related and that I will try to mention in the comments. I can also provide you with the maven artifact that I'm using.
was:
Hello guys,
I have found a problem in code generation when we use the feature "call a method on <variable>" from the Guided Rule Editor. An InvocationTargetException caused by a ClassCastException is thrown in RuleModelDRLPersistenceImpl.generateSetMethodCallsMethod method.
I have found other issues that I think are related and that I will try to mention in the comments. I can also provide you with the maven artifact that I'm using.
> Problems in code generation and parsing when a method is called from Guided Rules Editor
> ----------------------------------------------------------------------------------------
>
> Key: DROOLS-604
> URL: https://issues.jboss.org/browse/DROOLS-604
> Project: Drools
> Issue Type: Bug
> Affects Versions: 6.1.0.Final, 6.2.0.Beta1, 6.2.0.Beta2
> Reporter: Abel Marrero Santos
> Assignee: Mark Proctor
> Priority: Critical
> Attachments: model-base-0.0.1-SNAPSHOT.jar
>
>
> I have found a problem in code generation when we use the feature "call a method on <variable>" from the Guided Rule Editor. An InvocationTargetException caused by a ClassCastException is thrown in RuleModelDRLPersistenceImpl.generateSetMethodCallsMethod method.
> I have found other issues that I think are related and that I will try to mention in the comments. I can also provide you with the maven artifact that I'm using.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
9 years, 9 months
[JBoss JIRA] (WFLY-1067) Integrate JGroups with core AS security infrastructure
by Bela Ban (JIRA)
[ https://issues.jboss.org/browse/WFLY-1067?page=com.atlassian.jira.plugin.... ]
Bela Ban commented on WFLY-1067:
--------------------------------
Also note that we have customers which use multiple AUTH protocols in the same stack, e.g. X.509 and IP based authentication. In such a case, JGroups requires different IDs in the AUTH protocols, e.g.
{code:xml}
<AUTH ..../>
<AUTH id="3560" .../>
{code}
Wildfly therefore possibly needs to generate a unique ID to be used by JGroups.
> Integrate JGroups with core AS security infrastructure
> ------------------------------------------------------
>
> Key: WFLY-1067
> URL: https://issues.jboss.org/browse/WFLY-1067
> Project: WildFly
> Issue Type: Feature Request
> Components: Clustering, Security
> Reporter: Brian Stansberry
> Assignee: Richard Achmatowicz
>
> Container task for better integrating JGroups security with overall AS security. The basic concept is the various security aware aspects of JGroups will expose an SPI, and the AS can create implementations of those SPIs that integrate with the AS security realms. The AS JGroups subsystem will inject the implementation into the JGroups runtime components.
> Subtasks are for the various aspects. These can be done separately but a common overall design should be created to ensure a consistent approach is taken.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
9 years, 9 months
[JBoss JIRA] (WFLY-1951) ha-singleton ElectionPolicy breaks ha-singleton access on deferred startup of second node
by Paul Ferraro (JIRA)
[ https://issues.jboss.org/browse/WFLY-1951?page=com.atlassian.jira.plugin.... ]
Paul Ferraro updated WFLY-1951:
-------------------------------
Assignee: Richard Achmatowicz (was: Paul Ferraro)
> ha-singleton ElectionPolicy breaks ha-singleton access on deferred startup of second node
> -----------------------------------------------------------------------------------------
>
> Key: WFLY-1951
> URL: https://issues.jboss.org/browse/WFLY-1951
> Project: WildFly
> Issue Type: Bug
> Components: Clustering, EJB, Remoting
> Affects Versions: 8.0.0.Alpha4
> Reporter: Thomas Frühbeck
> Assignee: Richard Achmatowicz
>
> We want to use an election policy for ha-singleton service (SortedElectionPolicy with NamePreference).
> To assure, that only the singleton on the preferred node is accessed we also use a DeploymentNodeSelector implementing same preference.
> If the second node is started _after_ the first node is in full operation, the ClientContext is not notified of the existence of another node, and does not get the possibility to select the desired node according to cluster policy:
> Node "storage" in full operation:
> 07:32:30,006 INFO [at.tfr.test.service.ClusterDeploymentNodeSelector] (EJB default - 3) SELECTOR [storage]
> 07:32:30,027 INFO [at.tfr.test.service.ClusterDeploymentNodeSelector] (EJB default - 3) SELECTOR [storage]
> Node "NodeB" startup:
> 07:32:35,045 INFO [at.tfr.test.ClusterClient] (EJB default - 2) Service: Proxy for remote EJB StatelessEJBLocator{appName='', moduleName='wildfly-cluster', distinctName='', beanName='ClusterBean', view='interface at.tfr.test.ClusterRemote'}
> 07:32:35,048 INFO [at.tfr.test.service.ClusterDeploymentNodeSelector] (EJB default - 2) SELECTOR [NodeB, storage]
> Node "storage": NodeSelector still sees only "storage"
> 07:32:35,009 INFO [at.tfr.test.service.ClusterDeploymentNodeSelector] (EJB default - 4) SELECTOR [storage]
> 07:32:35,011 INFO [at.tfr.test.service.ClusterDeploymentNodeSelector] (EJB default - 4) SELECTOR [storage]
> If the ElectionPolicy now selected a node other than the currently active one ("NodeB" in this case), the access to the ha-singleton will fail, because "NodeB" is not selectable.
>
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
9 years, 9 months
[JBoss JIRA] (WFLY-2330) Test set org.jboss.as.test.clustering.cluster.registry.RegistryTestCase fails with NPE
by Paul Ferraro (JIRA)
[ https://issues.jboss.org/browse/WFLY-2330?page=com.atlassian.jira.plugin.... ]
Paul Ferraro closed WFLY-2330.
------------------------------
Fix Version/s: 9.0.0.Beta1
Resolution: Out of Date
> Test set org.jboss.as.test.clustering.cluster.registry.RegistryTestCase fails with NPE
> --------------------------------------------------------------------------------------
>
> Key: WFLY-2330
> URL: https://issues.jboss.org/browse/WFLY-2330
> Project: WildFly
> Issue Type: Bug
> Components: Clustering
> Affects Versions: 8.0.0.CR1
> Environment: Oracle JDK 1.7.0_45 on Solaris SPARC on SunBlade 2000.
> Reporter: Frank Langelage
> Assignee: Paul Ferraro
> Fix For: 9.0.0.Beta1
>
> Attachments: org.jboss.as.test.clustering.cluster.registry.RegistryTestCase-SYNC-tcp-output.txt, org.jboss.as.test.clustering.cluster.registry.RegistryTestCase-SYNC-tcp.txt, TEST-org.jboss.as.test.clustering.cluster.registry.RegistryTestCase-SYNC-tcp.xml
>
>
> Test org.jboss.as.test.clustering.cluster.registry.RegistryTestCase fails for me because of a NPE.
> See attached log files of this test.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
9 years, 9 months