[JBoss JIRA] (WFLY-11116) Wildfly 12.0.0 Final Delay in Getting the Value Attributes of the Session Variables (Result in Null Pointer Exception)
by ziad saade (Jira)
[ https://issues.jboss.org/browse/WFLY-11116?page=com.atlassian.jira.plugin... ]
ziad saade commented on WFLY-11116:
-----------------------------------
Hi Paul
any update from your side?
Best Regards
> Wildfly 12.0.0 Final Delay in Getting the Value Attributes of the Session Variables (Result in Null Pointer Exception)
> ----------------------------------------------------------------------------------------------------------------------
>
> Key: WFLY-11116
> URL: https://issues.jboss.org/browse/WFLY-11116
> Project: WildFly
> Issue Type: Bug
> Components: Clustering
> Affects Versions: 14.0.1.Final, 12.0.0.Final, 13.0.0.Final, 15.0.0.Final
> Reporter: ziad saade
> Assignee: Paul Ferraro
> Priority: Critical
>
> I have two Servlets Book and BookPreview the attribute is set in Book Servlet as follow:
>
> Book.java
> TestBean testBean=null;
> if(session.getAttribute("testBean")!=null)
> testBean = (TestBean)session.getAttribute("testBean");
> else{
> testBean=new TestBean();
> session.setAttribute("testBean",testBean);
> }
> testBean.setAmount("10");
>
> response.sendRedirect("BookPreview");
>
>
> The session attribute can be retrieved and the page is loaded normally and the Amount value is displayed however when submitting the form (Post Action in BookPreview.java) Null Pointer exception is generated.
>
> BookPreview.java
>
> TestBean testBean = (TestBean)session.getAttribute("testBean");
> String amount = testBean.getAmount; //Null pointer exception when submitting the form
>
> <form method="Post" action="BookPreview">
>
> </form>
>
> TestBean.java
>
> public class TestBean implements java.io.Serializable {
>
> private static final long serialVersionUID = 1L;
> private String amount;
>
> public String getAmount() {
> return amount;
> }
>
> public void setAmount(String amount) {
> this.amount = amount;
> }
> }
>
> Kindly advice how to fix the problem at the level of the server configuration.
> PS: I am not getting the exception when deploying the same application under other J EE application servers (Tomcat....)
>
> Thanks and Best Regards
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 2 months
[JBoss JIRA] (WFLY-12129) The subscribed topic is removed if reconnecting to messaging system with legacy-connection-factory
by terry liang (Jira)
[ https://issues.jboss.org/browse/WFLY-12129?page=com.atlassian.jira.plugin... ]
terry liang updated WFLY-12129:
-------------------------------
Steps to Reproduce:
1. Setup below configuration in wildfly
<subsystem xmlns="urn:jboss:domain:messaging-activemq:5.0">
<server name="default">
<security enabled="false"/>
<management jmx-enabled="true" address="jms.queue.activemq.management" jmx-domain="org.activemq" />
<security-setting name="activemq.management">
<role name="admin"/>
</security-setting>
<address-setting name="#" dead-letter-address="jms.queue.DLQ" expiry-address="jms.queue.ExpiryQueue" max-size-bytes="10485760000" page-size-bytes="2097152" message-counter-history-day-limit="10"/>
<http-connector name="http-connector" socket-binding="http" endpoint="http-acceptor"/>
<http-connector name="http-connector-throughput" socket-binding="http" endpoint="http-acceptor-throughput">
<param name="batch-delay" value="50"/>
</http-connector>
<remote-connector name="legacy-messaging-connector" socket-binding="legacy-messaging"/>
<in-vm-connector name="in-vm" server-id="0">
<param name="buffer-pooling" value="false"/>
</in-vm-connector>
<http-acceptor name="http-acceptor" http-listener="default"/>
<http-acceptor name="http-acceptor-throughput" http-listener="default">
<param name="batch-delay" value="50"/>
<param name="direct-deliver" value="false"/>
</http-acceptor>
<remote-acceptor name="legacy-messaging-acceptor" socket-binding="legacy-messaging"/>
<in-vm-acceptor name="in-vm" server-id="0">
<param name="buffer-pooling" value="false"/>
</in-vm-acceptor>
<jms-topic name="testTopic" entries="topic/newTestTopic java:jboss/exported/topic/newTestTopic" legacy-entries="topic/testTopic jms/topic/testTopic java:jboss/exported/topic/testTopic"/>
<connection-factory name="InVmConnectionFactory" entries="java:/ConnectionFactory java:jboss/exported/ConnectionFactory" connectors="in-vm"/>
<connection-factory name="NewRemoteConnectionFactory" entries="java:jboss/exported/jms/NewRemoteConnectionFactory" connectors="http-connector"/>
<legacy-connection-factory name="legacy-discovery" entries="java:jboss/exported/jms/RemoteConnectionFactory" connectors="legacy-messaging-connector"/>
<pooled-connection-factory name="activemq-ra" entries="java:/JmsXA java:jboss/DefaultJMSConnectionFactory" connectors="in-vm" transaction="xa"/>
</server>
</subsystem>
<subsystem xmlns="urn:jboss:domain:remoting:4.0">
<connector name="legacy-remoting-connector" socket-binding="legacy-remoting"/>
<http-connector name="http-remoting-connector" connector-ref="default"/>
</subsystem>
<interfaces>
<interface name="management">
<any-address/>
</interface>
<interface name="public">
<any-address/>
</interface>
<interface name="messaging-interface">
<any-address/>
</interface>
</interfaces>
<socket-binding-group name="standard-sockets" default-interface="public" port-offset="${my.jboss.port.offset:0}">
<socket-binding name="legacy-remoting" port="4447"/>
<socket-binding name="legacy-messaging" interface="messaging-interface" port="5445"/>
</socket-binding-group>
2. Use JMS client tool such as JMSToolBox to connect to wildfly messaging system with Apache Active MQ Artemis v2.x
3. Subscribe the topic testTopic
4. Disconnect to wildfly messaging system
5. Wait for 30 seconds
6. Reconnect to wildfly messaging system again
7. The topic testTopic disappear.
was:
1. Setup below configuration in wildfly
<subsystem xmlns="urn:jboss:domain:messaging-activemq:5.0">
<server name="default">
<security enabled="false"/>
<management jmx-enabled="true" address="jms.queue.activemq.management" jmx-domain="org.activemq" />
<security-setting name="activemq.management">
<role name="admin"/>
</security-setting>
<address-setting name="#" dead-letter-address="jms.queue.DLQ" expiry-address="jms.queue.ExpiryQueue" max-size-bytes="10485760000" page-size-bytes="2097152" message-counter-history-day-limit="10"/>
<http-connector name="http-connector" socket-binding="http" endpoint="http-acceptor"/>
<http-connector name="http-connector-throughput" socket-binding="http" endpoint="http-acceptor-throughput">
<param name="batch-delay" value="50"/>
</http-connector>
<remote-connector name="legacy-messaging-connector" socket-binding="legacy-messaging"/>
<in-vm-connector name="in-vm" server-id="0">
<param name="buffer-pooling" value="false"/>
</in-vm-connector>
<http-acceptor name="http-acceptor" http-listener="default"/>
<http-acceptor name="http-acceptor-throughput" http-listener="default">
<param name="batch-delay" value="50"/>
<param name="direct-deliver" value="false"/>
</http-acceptor>
<remote-acceptor name="legacy-messaging-acceptor" socket-binding="legacy-messaging"/>
<in-vm-acceptor name="in-vm" server-id="0">
<param name="buffer-pooling" value="false"/>
</in-vm-acceptor>
<jms-topic name="testTopic" entries="topic/newTestTopic java:jboss/exported/topic/newTestTopic" legacy-entries="topic/testTopic jms/topic/testTopic java:jboss/exported/topic/testTopic"/>
<connection-factory name="InVmConnectionFactory" entries="java:/ConnectionFactory java:jboss/exported/ConnectionFactory" connectors="in-vm"/>
<connection-factory name="NewRemoteConnectionFactory" entries="java:jboss/exported/jms/NewRemoteConnectionFactory" connectors="http-connector"/>
<legacy-connection-factory name="legacy-discovery" entries="java:jboss/exported/jms/RemoteConnectionFactory" connectors="legacy-messaging-connector"/>
<pooled-connection-factory name="activemq-ra" entries="java:/JmsXA java:jboss/DefaultJMSConnectionFactory" connectors="in-vm" transaction="xa"/>
</server>
</subsystem>
<subsystem xmlns="urn:jboss:domain:remoting:4.0">
<connector name="legacy-remoting-connector" socket-binding="legacy-remoting"/>
<http-connector name="http-remoting-connector" connector-ref="default"/>
</subsystem>
<interfaces>
<interface name="management">
<any-address/>
</interface>
<interface name="public">
<any-address/>
</interface>
<interface name="messaging-interface">
<any-address/>
</interface>
</interfaces>
<socket-binding-group name="standard-sockets" default-interface="public" port-offset="${msdp.jboss.port.offset:0}">
<socket-binding name="legacy-remoting" port="4447"/>
<socket-binding name="legacy-messaging" interface="messaging-interface" port="5445"/>
</socket-binding-group>
2. Use JMS client tool such as JMSToolBox to connect to wildfly messaging system with Apache Active MQ Artemis v2.x
3. Subscribe the topic testTopic
4. Disconnect to wildfly messaging system
5. Wait for 30 seconds
6. Reconnect to wildfly messaging system again
7. The topic testTopic disappear.
> The subscribed topic is removed if reconnecting to messaging system with legacy-connection-factory
> --------------------------------------------------------------------------------------------------
>
> Key: WFLY-12129
> URL: https://issues.jboss.org/browse/WFLY-12129
> Project: WildFly
> Issue Type: Bug
> Components: JMS
> Affects Versions: 17.0.0.Alpha1, 17.0.0.Beta1
> Reporter: terry liang
> Assignee: Emmanuel Hugonnet
> Priority: Major
> Labels: regression
>
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 2 months
[JBoss JIRA] (WFLY-12127) ClientClusterNodeSelectorTestCase leaks CustomClusterNodeSelector to other tests
by Radoslav Husar (Jira)
[ https://issues.jboss.org/browse/WFLY-12127?page=com.atlassian.jira.plugin... ]
Radoslav Husar updated WFLY-12127:
----------------------------------
Issue Type: Task (was: Bug)
> ClientClusterNodeSelectorTestCase leaks CustomClusterNodeSelector to other tests
> --------------------------------------------------------------------------------
>
> Key: WFLY-12127
> URL: https://issues.jboss.org/browse/WFLY-12127
> Project: WildFly
> Issue Type: Task
> Components: Clustering, Test Suite
> Affects Versions: 13.0.0.Final
> Reporter: Radoslav Husar
> Assignee: Radoslav Husar
> Priority: Minor
>
> {noformat}
> [ERROR] Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 5.824 s <<< FAILURE! - in org.jboss.as.test.clustering.cluster.ejb.remote.ClientRemoteStatelessEJBFailoverTestCase
> [ERROR] test(org.jboss.as.test.clustering.cluster.ejb.remote.ClientRemoteStatelessEJBFailoverTestCase) Time elapsed: 5.809 s <<< ERROR!
> java.lang.IllegalStateException: EJBCLIENT000076: Configured selector "org.jboss.as.test.clustering.cluster.ejb.remote.ClientClusterNodeSelectorTestCase$CustomClusterNodeSelector@59532566" returned unknown node "node-3"
> {noformat}
> Introduced in f3577724aabac8f3104b35e696f0c9d16b6797ca
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 2 months
[JBoss JIRA] (WFLY-12128) NPE in StatefulSessionSynchronizationInterceptor.java:210
by Cheng Fang (Jira)
[ https://issues.jboss.org/browse/WFLY-12128?page=com.atlassian.jira.plugin... ]
Cheng Fang commented on WFLY-12128:
-----------------------------------
I couldn't reproduce the error in my local environment:
{code}
/Users/cfang/dev/wildfly/testsuite/integration/clustering > mvn clean install -Dts.noSmoke -Dts.clustering -Dtest=org.jboss.as.test.clustering.cluster.ejb.remote.TransactionalRemoteStatefulEJBFailoverTestCase
... ...
[INFO] T E S T S
[INFO] -------------------------------------------------------
[INFO] Running org.jboss.as.test.clustering.cluster.ejb.remote.TransactionalRemoteStatefulEJBFailoverTestCase
[INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 28.444 s - in org.jboss.as.test.clustering.cluster.ejb.remote.TransactionalRemoteStatefulEJBFailoverTestCase
[INFO]
[INFO] Results:
[INFO]
[INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0
[INFO]
{code}
Do you always see this failure or is it intermittent for you?
> NPE in StatefulSessionSynchronizationInterceptor.java:210
> ---------------------------------------------------------
>
> Key: WFLY-12128
> URL: https://issues.jboss.org/browse/WFLY-12128
> Project: WildFly
> Issue Type: Bug
> Components: EJB, Transactions
> Affects Versions: 17.0.0.Alpha1
> Reporter: Radoslav Husar
> Assignee: Cheng Fang
> Priority: Major
>
> Reproducer
> {code}
> ./integration-tests.sh clean install -Dts.noSmoke -Dts.clustering -Dtest=org.jboss.as.test.clustering.cluster.ejb.remote.TransactionalRemoteStatefulEJBFailoverTestCase
> {code}
> {noformat}
> .[0m.[33m18:10:40,409 WARN [org.jboss.as.txn] (default task-2) WFLYTX0027: The pre-jca synchronization org.jboss.as.ejb3.component.stateful.StatefulSessionSynchronizationInterceptor$StatefulSessionSynchronization@f525ed4 associated with tx Local transaction (delegate=T
> ransactionImple < ac, BasicAction: 0:ffffc0a80002:-642358e3:5ce8176c:3d status: ActionStatus.ABORTED >, owner=Local transaction context for provider JBoss JTA transaction provider) failed during after completion: java.lang.NullPointerException
> at org.jboss.as.ejb3.component.stateful.StatefulSessionSynchronizationInterceptor.releaseInstance(StatefulSessionSynchronizationInterceptor.java:210)
> at org.jboss.as.ejb3.component.stateful.StatefulSessionSynchronizationInterceptor.handleAfterCompletion(StatefulSessionSynchronizationInterceptor.java:297)
> at org.jboss.as.ejb3.component.stateful.StatefulSessionSynchronizationInterceptor$StatefulSessionSynchronization.afterCompletion(StatefulSessionSynchronizationInterceptor.java:270)
> at org.jboss.as.txn.service.internal.tsr.JCAOrderedLastSynchronizationList.afterCompletion(JCAOrderedLastSynchronizationList.java:144)
> at org.wildfly.transaction.client.AbstractTransaction.performConsumer(AbstractTransaction.java:223)
> at org.wildfly.transaction.client.AbstractTransaction$AssociatingSynchronization.afterCompletion(AbstractTransaction.java:306)
> at com.arjuna.ats.internal.jta.resources.arjunacore.SynchronizationImple.afterCompletion(SynchronizationImple.java:96)
> at com.arjuna.ats.arjuna.coordinator.TwoPhaseCoordinator.afterCompletion(TwoPhaseCoordinator.java:545)
> at com.arjuna.ats.arjuna.coordinator.TwoPhaseCoordinator.afterCompletion(TwoPhaseCoordinator.java:472)
> at com.arjuna.ats.arjuna.coordinator.TwoPhaseCoordinator.cancel(TwoPhaseCoordinator.java:127)
> at com.arjuna.ats.arjuna.AtomicAction.cancel(AtomicAction.java:215)
> at com.arjuna.ats.internal.jta.transaction.arjunacore.TransactionImple.rollback(TransactionImple.java:284)
> at org.wildfly.transaction.client.provider.jboss.JBossLocalTransactionProvider$Entry.rollbackLocal(JBossLocalTransactionProvider.java:353)
> at org.wildfly.transaction.client.provider.jboss.JBossJTALocalTransactionProvider.rollbackLocal(JBossJTALocalTransactionProvider.java:132)
> at org.wildfly.transaction.client.LocalTransaction.rollback(LocalTransaction.java:93)
> at org.wildfly.transaction.client.AbstractTransaction.performConsumer(AbstractTransaction.java:241)
> at org.wildfly.transaction.client.AbstractTransaction.performConsumer(AbstractTransaction.java:247)
> at org.wildfly.transaction.client.AbstractTransaction.performAction(AbstractTransaction.java:267)
> at org.wildfly.transaction.client.provider.remoting.TransactionServerChannel.lambda$handleUserTxnRollback$0(TransactionServerChannel.java:223)
> at org.wildfly.security.auth.server.SecurityIdentity.runAsConsumer(SecurityIdentity.java:361)
> at org.wildfly.security.auth.server.Scoped.runAsConsumer(Scoped.java:112)
> at org.wildfly.security.auth.server.Scoped.runAs(Scoped.java:60)
> at org.wildfly.transaction.client.provider.remoting.TransactionServerChannel.handleUserTxnRollback(TransactionServerChannel.java:220)
> at org.wildfly.transaction.client.provider.remoting.TransactionServerChannel$ReceiverImpl.handleMessage(TransactionServerChannel.java:99)
> at org.jboss.remoting3.remote.RemoteConnectionChannel.lambda$handleMessageData$3(RemoteConnectionChannel.java:430)
> at org.jboss.remoting3.EndpointImpl$TrackingExecutor.lambda$execute$0(EndpointImpl.java:942)
> at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
> at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1982)
> at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1486)
> at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1377)
> at java.lang.Thread.run(Thread.java:748)
> {noformat}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 2 months
[JBoss JIRA] (LOGMGR-246) Wildfly 16 incorrect working log zip rotator
by James Perkins (Jira)
[ https://issues.jboss.org/browse/LOGMGR-246?page=com.atlassian.jira.plugin... ]
James Perkins updated LOGMGR-246:
---------------------------------
Priority: Critical (was: Major)
> Wildfly 16 incorrect working log zip rotator
> --------------------------------------------
>
> Key: LOGMGR-246
> URL: https://issues.jboss.org/browse/LOGMGR-246
> Project: JBoss Log Manager
> Issue Type: Bug
> Components: core
> Environment: Windows,
> Oracle JDK 8
> Reporter: Igor Dmitriev
> Assignee: James Perkins
> Priority: Critical
> Fix For: 1.5.10.Final, 2.0.12.Final, 2.1.11.Final, 2.2.0.Final, 3.0.0.Final
>
>
> My logging profile configuration is:
> 1)
> {code:xml}
> <periodic-size-rotating-file-handler name="FILE" rotate-on-boot="false" autoflush="true">
> <level name="ALL"/>
> <file relative-to="jboss.server.log.dir" path="corp.log"/>
> <rotate-size value="300k"/>
> <max-backup-index value="10000"/>
> <suffix value=".yyyy-MM-dd.zip"/>
> <append value="true"/>
> </periodic-size-rotating-file-handler>
> {code}
> File corp.log increase it size permanently, even after new corp.log.yyyy-MM-dd.N.zip file created. Due it, each .zip archive contain same corp.log with maximum current size.
> 2)
> {code:xml}
> <periodic-size-rotating-file-handler name="FILE2" rotate-on-boot="true" autoflush="true">
> <level name="ALL"/>
> <file relative-to="jboss.server.log.dir" path="corp.log"/>
> <rotate-size value="300k"/>
> <max-backup-index value="10000"/>
> <suffix value=".yyyy-MM-dd.zip"/>
> <append value="false"/>
> </periodic-size-rotating-file-handler>
> {code}
> All work as expected, except each time corp.log reach 300k, appear pair .zip files with same content?
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 2 months
[JBoss JIRA] (WFLY-11794) Helloworld-classtransformer incompatibility
by Eduardo Martins (Jira)
[ https://issues.jboss.org/browse/WFLY-11794?page=com.atlassian.jira.plugin... ]
Eduardo Martins reassigned WFLY-11794:
--------------------------------------
Assignee: Richard Opalka (was: Eduardo Martins)
> Helloworld-classtransformer incompatibility
> -------------------------------------------
>
> Key: WFLY-11794
> URL: https://issues.jboss.org/browse/WFLY-11794
> Project: WildFly
> Issue Type: Bug
> Components: Quickstarts
> Reporter: Eduardo Martins
> Assignee: Richard Opalka
> Priority: Major
>
> Changes done at server side, wrt JDK12 compatibility, introduced issues when deploying quickstart helloworld-classtransformer post WFLY 16 Beta:
> {code}
> 22:37:27,320 INFO [org.jboss.as.repository] (management-handler-thread - 1) WFLYDR0001: Content added at location /Users/emmartins/jboss/git/as/wildfly/dist-copy/target/wildfly-16.0.0.CR1-SNAPSHOT/standalone/data/content/23/641c0517f5106bee30dbc931cc7fe8784f52d7/content
> 22:37:27,350 INFO [org.jboss.as.server.deployment] (MSC service thread 1-8) WFLYSRV0027: Starting deployment of "helloworld-classfiletransformers.war" (runtime-name: "helloworld-classfiletransformers.war")
> 22:37:28,051 WARN [org.jboss.as.dependency.private] (MSC service thread 1-4) WFLYSRV0018: Deployment "deployment.helloworld-classfiletransformers.war" is using a private module ("org.javassist") which may be changed or removed in future versions without notice.
> 22:37:28,108 INFO [hello.server.transformation.HelloByteCodeManipulator] (MSC service thread 1-8) Instrumenting hello.server.ejb.HelloBean
> 22:37:28,166 INFO [hello.server.transformation.HelloByteCodeManipulator] (MSC service thread 1-8) Successfully instrumented hello.server.ejb.HelloBean
> 22:37:28,206 INFO [org.jboss.weld.deployer] (MSC service thread 1-8) WFLYWELD0003: Processing weld deployment helloworld-classfiletransformers.war
> 22:37:28,449 INFO [org.hibernate.validator.internal.util.Version] (MSC service thread 1-8) HV000001: Hibernate Validator 6.0.15.Final
> 22:37:28,699 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-8) WFLYEJB0473: JNDI bindings for session bean named 'HelloBean' in deployment unit 'deployment "helloworld-classfiletransformers.war"' are as follows:
> WARNING: An illegal reflective access operation has occurred
> WARNING: Illegal reflective access by org.jboss.invocation.proxy.AbstractProxyFactory$1 (jar:file:/Users/emmartins/jboss/git/as/wildfly/dist-copy/target/wildfly-16.0.0.CR1-SNAPSHOT/modules/system/layers/base/org/jboss/invocation/main/jboss-invocation-1.5.2.Final.jar!/) to method java.lang.Object.clone()
> WARNING: Please consider reporting this to the maintainers of org.jboss.invocation.proxy.AbstractProxyFactory$1
> WARNING: Use --illegal-access=warn to enable warnings of further illegal reflective access operations
> WARNING: All illegal access operations will be denied in a future release
> 22:37:29,062 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-3) MSC000001: Failed to start service jboss.deployment.unit."helloworld-classfiletransformers.war".INSTALL: org.jboss.msc.service.StartException in service jboss.deployment.unit."helloworld-classfiletransformers.war".INSTALL: WFLYSRV0153: Failed to process phase INSTALL of deployment "helloworld-classfiletransformers.war"
> at org.jboss.as.server@8.0.0.CR1//org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:183)
> at org.jboss.msc@1.4.5.Final//org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1738)
> at org.jboss.msc@1.4.5.Final//org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1700)
> at org.jboss.msc@1.4.5.Final//org.jboss.msc.service.ServiceControllerImpl$ControllerTask.run(ServiceControllerImpl.java:1558)
> at org.jboss.threads@2.3.3.Final//org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
> at org.jboss.threads@2.3.3.Final//org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1982)
> at org.jboss.threads@2.3.3.Final//org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1486)
> at org.jboss.threads@2.3.3.Final//org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1377)
> at java.base/java.lang.Thread.run(Thread.java:834)
> Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: WFLYEE0024: Could not configure component HelloBean
> at org.jboss.as.ee@16.0.0.CR1-SNAPSHOT//org.jboss.as.ee.component.deployers.EEModuleConfigurationProcessor.deploy(EEModuleConfigurationProcessor.java:106)
> at org.jboss.as.server@8.0.0.CR1//org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:176)
> ... 8 more
> Caused by: java.lang.ClassFormatError: javassist.NotFoundException: hello.server.ejb.HelloBean$$$view1
> at org.jboss.modules.ModuleClassLoader.defineClassInternal(ModuleClassLoader.java:460)
> at org.jboss.modules.ModuleClassLoader.defineClassInternal(ModuleClassLoader.java:480)
> at org.jboss.modules.ClassDefiner.defineClass(ClassDefiner.java:144)
> at org.jboss.as.server@8.0.0.CR1//org.jboss.as.server.deployment.ModuleClassFactory.defineClass(ModuleClassFactory.java:56)
> at org.jboss.classfilewriter@1.2.4.Final//org.jboss.classfilewriter.ClassFile.defineInternal(ClassFile.java:299)
> at org.jboss.classfilewriter@1.2.4.Final//org.jboss.classfilewriter.ClassFile.define(ClassFile.java:286)
> at org.jboss.invocation@1.5.2.Final//org.jboss.invocation.proxy.AbstractClassFactory.defineClass(AbstractClassFactory.java:202)
> at org.jboss.invocation@1.5.2.Final//org.jboss.invocation.proxy.AbstractProxyFactory.getCachedMethods(AbstractProxyFactory.java:162)
> at org.jboss.as.ejb3@16.0.0.CR1-SNAPSHOT//org.jboss.as.ejb3.component.stateless.StatelessComponentDescription$3.configure(StatelessComponentDescription.java:147)
> at org.jboss.as.ee@16.0.0.CR1-SNAPSHOT//org.jboss.as.ee.component.DefaultComponentViewConfigurator.configure(DefaultComponentViewConfigurator.java:91)
> at org.jboss.as.ee@16.0.0.CR1-SNAPSHOT//org.jboss.as.ee.component.deployers.EEModuleConfigurationProcessor.deploy(EEModuleConfigurationProcessor.java:92)
> ... 9 more
> Caused by: java.lang.RuntimeException: javassist.NotFoundException: hello.server.ejb.HelloBean$$$view1
> at deployment.helloworld-classfiletransformers.war//hello.server.transformation.HelloByteCodeManipulator.getCtClass(HelloByteCodeManipulator.java:135)
> at deployment.helloworld-classfiletransformers.war//hello.server.transformation.HelloByteCodeManipulator.transform(HelloByteCodeManipulator.java:70)
> at deployment.helloworld-classfiletransformers.war//hello.server.transformation.HelloBeanClassFileTransformer.transform(HelloBeanClassFileTransformer.java:57)
> at org.jboss.as.server@8.0.0.CR1//org.jboss.as.server.deployment.module.DelegatingClassFileTransformer.transform(DelegatingClassFileTransformer.java:60)
> at org.jboss.modules.JLIClassTransformer.transform(JLIClassTransformer.java:55)
> at org.jboss.modules.ModuleClassLoader.defineClassInternal(ModuleClassLoader.java:458)
> ... 19 more
> Caused by: javassist.NotFoundException: hello.server.ejb.HelloBean$$$view1
> at org.javassist//javassist.ClassPool.get(ClassPool.java:422)
> at deployment.helloworld-classfiletransformers.war//hello.server.transformation.HelloByteCodeManipulator.getCtClass(HelloByteCodeManipulator.java:133)
> ... 24 more
> 22:37:29,154 INFO [org.infinispan.factories.GlobalComponentRegistry] (MSC service thread 1-6) ISPN000128: Infinispan version: Infinispan 'Infinity Minus ONE +2' 9.4.8.Final
> 22:37:29,620 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 74) WFLYCLINF0002: Started client-mappings cache from ejb container
> 22:37:29,695 ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 1) WFLYCTL0013: Operation ("add") failed - address: ([("deployment" => "helloworld-classfiletransformers.war")]) - failure description: {
> "WFLYCTL0080: Failed services" => {"jboss.deployment.unit.\"helloworld-classfiletransformers.war\".INSTALL" => "WFLYSRV0153: Failed to process phase INSTALL of deployment \"helloworld-classfiletransformers.war\"
> Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: WFLYEE0024: Could not configure component HelloBean
> Caused by: java.lang.ClassFormatError: javassist.NotFoundException: hello.server.ejb.HelloBean$$$view1
> Caused by: java.lang.RuntimeException: javassist.NotFoundException: hello.server.ejb.HelloBean$$$view1
> Caused by: javassist.NotFoundException: hello.server.ejb.HelloBean$$$view1"},
> "WFLYCTL0412: Required services that are not installed:" => [
> "jboss.deployment.unit.\"helloworld-classfiletransformers.war\".beanmanager",
> "jboss.deployment.unit.\"helloworld-classfiletransformers.war\".WeldStartService"
> ],
> "WFLYCTL0180: Services with missing/unavailable dependencies" => [
> "jboss.deployment.unit.\"helloworld-classfiletransformers.war\".weld.weldClassIntrospector is missing [jboss.deployment.unit.\"helloworld-classfiletransformers.war\".WeldStartService, jboss.deployment.unit.\"helloworld-classfiletransformers.war\".beanmanager]",
> "jboss.deployment.unit.\"helloworld-classfiletransformers.war\".batch.artifact.factory is missing [jboss.deployment.unit.\"helloworld-classfiletransformers.war\".beanmanager]"
> ]
> }
> 22:37:29,697 ERROR [org.jboss.as.server] (management-handler-thread - 1) WFLYSRV0021: Deploy of deployment "helloworld-classfiletransformers.war" was rolled back with the following failure message:
> {
> "WFLYCTL0080: Failed services" => {"jboss.deployment.unit.\"helloworld-classfiletransformers.war\".INSTALL" => "WFLYSRV0153: Failed to process phase INSTALL of deployment \"helloworld-classfiletransformers.war\"
> Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: WFLYEE0024: Could not configure component HelloBean
> Caused by: java.lang.ClassFormatError: javassist.NotFoundException: hello.server.ejb.HelloBean$$$view1
> Caused by: java.lang.RuntimeException: javassist.NotFoundException: hello.server.ejb.HelloBean$$$view1
> Caused by: javassist.NotFoundException: hello.server.ejb.HelloBean$$$view1"},
> "WFLYCTL0412: Required services that are not installed:" => [
> "jboss.deployment.unit.\"helloworld-classfiletransformers.war\".beanmanager",
> "jboss.deployment.unit.\"helloworld-classfiletransformers.war\".WeldStartService"
> ],
> "WFLYCTL0180: Services with missing/unavailable dependencies" => [
> "jboss.deployment.unit.\"helloworld-classfiletransformers.war\".weld.weldClassIntrospector is missing [jboss.deployment.unit.\"helloworld-classfiletransformers.war\".WeldStartService, jboss.deployment.unit.\"helloworld-classfiletransformers.war\".beanmanager]",
> "jboss.deployment.unit.\"helloworld-classfiletransformers.war\".batch.artifact.factory is missing [jboss.deployment.unit.\"helloworld-classfiletransformers.war\".beanmanager]"
> ]
> }
> 22:37:29,727 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0028: Stopped deployment helloworld-classfiletransformers.war (runtime-name: helloworld-classfiletransformers.war) in 29ms
> {code}
> It's not clear the actual QS design is something we want to keep promoting tho:
> * it teaches how to use a private module
> * we use byteman with users/customers, when intercepting code on the fly
> Assuming incompatibility we should drop the QS from WFLY releases, and we should rethink if we going to fix it, or replace it with a new QS.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 2 months
[JBoss JIRA] (WFLY-1598) Out of the box SSL - or shortly after.
by James Perkins (Jira)
[ https://issues.jboss.org/browse/WFLY-1598?page=com.atlassian.jira.plugin.... ]
James Perkins updated WFLY-1598:
--------------------------------
Fix Version/s: 17.0.0.Final
(was: 17.0.0.Beta1)
> Out of the box SSL - or shortly after.
> --------------------------------------
>
> Key: WFLY-1598
> URL: https://issues.jboss.org/browse/WFLY-1598
> Project: WildFly
> Issue Type: Sub-task
> Components: Management, Security
> Reporter: Darran Lofthouse
> Assignee: Farah Juma
> Priority: Critical
> Labels: management_security,, management_sso
> Fix For: 17.0.0.Final
>
>
> There are various reasons that we do not support SSL/TLS out of the box e.g.
> - If we ship a default keystore then everyone has access to the private key.
> - Generating one on first boot we do not have sufficient information to generate it correctly, also the performance overhead.
> This issue is to explorer other options to encourage their use and make it easier to configure.
> As an example could the admin console detect a non encrypted connection and have an box that encourages the config along with a wizard like workflow to get it set up?
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 2 months
[JBoss JIRA] (WFLY-11073) Support hex encoding in jdbc-realm for elytron
by James Perkins (Jira)
[ https://issues.jboss.org/browse/WFLY-11073?page=com.atlassian.jira.plugin... ]
James Perkins updated WFLY-11073:
---------------------------------
Fix Version/s: 17.0.0.Final
(was: 17.0.0.Beta1)
> Support hex encoding in jdbc-realm for elytron
> ----------------------------------------------
>
> Key: WFLY-11073
> URL: https://issues.jboss.org/browse/WFLY-11073
> Project: WildFly
> Issue Type: Feature Request
> Components: Documentation, Security
> Reporter: Jan Kalina
> Assignee: Darran Lofthouse
> Priority: Major
> Labels: elytron
> Fix For: 17.0.0.Final
>
>
> Old database login-module can be configured passing the attribute {{hashEncoding}}, for example:
> {code:xml}
> <login-module code="Database" flag="required">
> <module-option name="dsJndiName" value="java:jboss/datasources/ExampleDS"/>
> <module-option name="principalsQuery" value="SELECT password FROM User WHERE username = ?"/>
> <module-option name="rolesQuery" value="SELECT role, 'Roles' FROM User WHERE username = ?"/>
> <module-option name="hashAlgorithm" value="SHA-1"/>
> <module-option name="hashEncoding" value="hex"/>
> <module-option name="hashCharset" value="UTF-8"/>
> </login-module>
> {code}
> Currently jdbc-realm in elytron only uses base64 encoding if hash is stored in a text column. This way the migration is more complicated cos the password hash is not valid changing from old security system to elytron.
> Think also about the charset attribute.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 2 months