[JBoss JIRA] Created: (JBAS-8139) Ability to rollback AS version updates
by Brian Stansberry (JIRA)
Ability to rollback AS version updates
--------------------------------------
Key: JBAS-8139
URL: https://jira.jboss.org/browse/JBAS-8139
Project: JBoss Application Server
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: Domain Management
Reporter: Brian Stansberry
Fix For: Unscheduled
This JIRA is based on feedback we received after the Andiamo BOF at JBoss World 2010:
>> A fixpack installer that handles version rollbacks would be fantastic.
>> Of course it needs to remain flexible to work with JBoss installs that
>> have been manually modified.
Note that this may be out of scope for community AS 7; e.g. it may be a JON function. However, the AS 7 design of things like how we lay down content on the filesystem should take this use case into account.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 5 months
[JBoss JIRA] Created: (JBAS-8842) Security checks when recursively reading resources
by Emanuel Muckenhuber (JIRA)
Security checks when recursively reading resources
--------------------------------------------------
Key: JBAS-8842
URL: https://issues.jboss.org/browse/JBAS-8842
Project: JBoss Application Server
Issue Type: Task
Security Level: Public (Everyone can see)
Affects Versions: 7.0.0.Alpha1
Reporter: Emanuel Muckenhuber
Assignee: Darran Lofthouse
Currently the "read-resource" operation (GlobalOperationHandlers.ReadResourceHandler) just clones the subModel when recursively reading resources. We need to make sure that to also check the permissions for the children a node contains.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 5 months
[JBoss JIRA] Created: (AS7-1103) Intermittent failures in org.jboss.as.controller.CompositeOperationHandlerUnitTestCase
by James Perkins (JIRA)
Intermittent failures in org.jboss.as.controller.CompositeOperationHandlerUnitTestCase
--------------------------------------------------------------------------------------
Key: AS7-1103
URL: https://issues.jboss.org/browse/AS7-1103
Project: Application Server 7
Issue Type: Bug
Reporter: James Perkins
Assignee: Brian Stansberry
Fix For: 7.0.0.CR1
Below is the message from the error.
-------------------------------------------------------------------------------
Test set: org.jboss.as.controller.CompositeOperationHandlerUnitTestCase
-------------------------------------------------------------------------------
Tests run: 24, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 1.625 sec <<< FAILURE!
testRestartRequired(org.jboss.as.controller.CompositeOperationHandlerUnitTestCase) Time elapsed: 0.031 sec <<< FAILURE!
org.junit.ComparisonFailure: expected:<[restart-requir]ed> but was:<[undefin]ed>
at org.junit.Assert.assertEquals(Assert.java:123)
at org.junit.Assert.assertEquals(Assert.java:145)
at org.jboss.as.controller.CompositeOperationHandlerUnitTestCase.testRestartRequired(CompositeOperationHandlerUnitTestCase.java:496)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:44)
at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15)
at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:41)
at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:20)
at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:28)
at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:31)
at org.junit.runners.BlockJUnit4ClassRunner.runNotIgnored(BlockJUnit4ClassRunner.java:79)
at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:71)
at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:49)
at org.junit.runners.ParentRunner$3.run(ParentRunner.java:193)
at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:52)
at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:191)
at org.junit.runners.ParentRunner.access$000(ParentRunner.java:42)
at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:184)
at org.junit.runners.ParentRunner.run(ParentRunner.java:236)
at org.apache.maven.surefire.junit4.JUnit4TestSet.execute(JUnit4TestSet.java:53)
at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:119)
at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:101)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.apache.maven.surefire.booter.ProviderFactory$ClassLoaderProxy.invoke(ProviderFactory.java:103)
at $Proxy0.invoke(Unknown Source)
at org.apache.maven.surefire.booter.SurefireStarter.invokeProvider(SurefireStarter.java:150)
at org.apache.maven.surefire.booter.SurefireStarter.runSuitesInProcess(SurefireStarter.java:91)
at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:69)
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 5 months
[JBoss JIRA] Created: (AS7-762) Provide an operation to request service status report after server has been started
by Heiko Braun (JIRA)
Provide an operation to request service status report after server has been started
-------------------------------------------------------------------------------------
Key: AS7-762
URL: https://issues.jboss.org/browse/AS7-762
Project: Application Server 7
Issue Type: Feature Request
Components: Domain Management
Reporter: Heiko Braun
Assignee: Brian Stansberry
For proper healthcare it would beneficial if I could verify the server status after is has been started. I.e. to catch these, which currently only appear in the server log:
[Server:server-three] 17:48:26,636 INFO [org.jboss.as.server] (MSC service thread 1-2) Service status report
[Server:server-three] New missing/unsatisfied dependencies:
[Server:server-three] service jboss.binding.http2 (missing)
[Server:server-three]
[Server:server-three] 17:48:26,636 ERROR [org.jboss.as] (MSC service thread 1-4) JBoss AS 7.0.0.Beta4-SNAPSHOT "(TBD)" started (with errors) in 3893ms - Started 101 of 149 services (1 services failed or missing dependencies, 47 services are passive or on-demand)
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 5 months
[JBoss JIRA] Created: (JBAS-8635) MailResourceAdapter mail check triggered only once
by Martin Clauss (JIRA)
MailResourceAdapter mail check triggered only once
--------------------------------------------------
Key: JBAS-8635
URL: https://jira.jboss.org/browse/JBAS-8635
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: JCA service
Affects Versions: 6.0.0.M5
Environment: Win7, JBoss 6.0.0.M5, Java 1.6.0_21
Ubuntu lucid, JBoss 6.0.0.M5, Java 1.6.0_18
Reporter: Martin Clauss
Assignee: Jesper Pedersen
Mail check is performed correctly only once (after first timeout of pollingInterval) and then never again...
18:43:13,690 INFO [org.jboss.ejb3.deployers.JBossASKernel] installing bean: jboss.j2ee:ear=CTAEar.ear,jar=CTAEJB3.jar,name=MailBean,service=EJB3
18:43:13,690 INFO [org.jboss.ejb3.deployers.JBossASKernel] with dependencies:
18:43:13,690 INFO [org.jboss.ejb3.deployers.JBossASKernel] and demands:
18:43:13,690 INFO [org.jboss.ejb3.deployers.JBossASKernel] jboss.ejb:service=EJBTimerService; Required: Described
18:43:13,690 INFO [org.jboss.ejb3.deployers.JBossASKernel] and supplies:
18:43:13,690 INFO [org.jboss.ejb3.deployers.JBossASKernel] jndi:null
18:43:13,691 INFO [org.jboss.ejb3.deployers.JBossASKernel] Class:org.jboss.resource.adapter.mail.inflow.MailListener
18:43:13,691 INFO [org.jboss.ejb3.deployers.JBossASKernel] Added bean(jboss.j2ee:ear=CTAEar.ear,jar=CTAEJB3.jar,name=MailBean,service=EJB3) to KernelDeployment of: CTAEJB3.jar
18:43:13,741 INFO [org.jboss.ejb3.EJBContainer] STARTED EJB: com.contactulater.ba.MailBean ejbName: MailBean
****snip****
18:44:13,749 INFO [STDOUT] DEBUG: JavaMail version 1.4.2
18:44:13,760 INFO [STDOUT] DEBUG: successfully loaded resource: /META-INF/javamail.default.providers
18:44:13,761 INFO [STDOUT] DEBUG: Tables of loaded providers
18:44:13,761 INFO [STDOUT] DEBUG: Providers Listed By Class Name: {com.sun.mail.smtp.SMTPSSLTransport=javax.mail.Provider ***snip***
18:44:13,763 INFO [STDOUT] DEBUG: successfully loaded resource: /META-INF/javamail.default.address.map
18:44:13,771 INFO [STDOUT] DEBUG: setDebug: JavaMail version 1.4.2
18:44:13,771 INFO [STDOUT] DEBUG: getProvider() returning javax.mail.Provider[STORE,imap,com.sun.mail.imap.IMAPStore,Sun Microsystems, Inc]
18:44:13,772 INFO [STDOUT] DEBUG: mail.imap.fetchsize: 16384
18:44:13,772 INFO [STDOUT] DEBUG: mail.imap.statuscachetimeout: 1000
18:44:13,773 INFO [STDOUT] DEBUG: mail.imap.appendbuffersize: -1
18:44:13,773 INFO [STDOUT] DEBUG: mail.imap.minidletime: 10
18:44:13,774 INFO [STDOUT] DEBUG: trying to connect to host "127.0.0.1", port 143, isSSL false
18:44:13,799 INFO [STDOUT] * OK **** Cyrus IMAP4 v2.2.13-Debian-2.2.13-19 server ready
18:44:13,800 INFO [STDOUT] A0 CAPABILITY
18:44:13,820 INFO [STDOUT] * CAPABILITY IMAP4 IMAP4rev1 ACL QUOTA LITERAL+ NAMESPACE UIDPLUS ID NO_ATOMIC_RENAME UNSELECT CHILDREN MULTIAPPEND BINARY SORT THREAD=ORDEREDSUBJECT THREAD=REFERENCES ANNOTATEMORE IDLE STARTTLS
18:44:13,821 INFO [STDOUT] A0 OK Completed
18:44:13,821 INFO [STDOUT] DEBUG: protocolConnect login, host=127.0.0.1, user=jbossra, password=<non-null>
18:44:13,844 INFO [STDOUT] A1 OK User logged in
18:44:13,845 INFO [STDOUT] A2 CAPABILITY
18:44:13,868 INFO [STDOUT] * CAPABILITY IMAP4 IMAP4rev1 ACL QUOTA LITERAL+ NAMESPACE UIDPLUS ID NO_ATOMIC_RENAME UNSELECT CHILDREN MULTIAPPEND BINARY SORT THREAD=ORDEREDSUBJECT THREAD=REFERENCES ANNOTATEMORE IDLE LOGINDISABLED
18:44:13,869 INFO [STDOUT] A2 OK Completed
18:44:13,870 INFO [STDOUT] A3 LIST "" INBOX
18:44:13,889 INFO [STDOUT] * LIST (\HasChildren) "." "INBOX"
18:44:13,890 INFO [STDOUT] A3 OK Completed (0.000 secs 4 calls)
18:44:13,891 INFO [STDOUT] DEBUG: connection available -- size: 1
18:44:13,891 INFO [STDOUT] A4 SELECT INBOX
18:44:13,973 INFO [STDOUT] * FLAGS (\Answered \Flagged \Draft \Deleted \Seen)
18:44:13,973 INFO [STDOUT] * OK [PERMANENTFLAGS (\Answered \Flagged \Draft \Deleted \Seen \*)]
18:44:13,973 INFO [STDOUT] * 2 EXISTS
18:44:13,974 INFO [STDOUT] * 0 RECENT
18:44:13,974 INFO [STDOUT] * OK [UIDVALIDITY 1288029487]
18:44:13,974 INFO [STDOUT] * OK [UIDNEXT 4]
18:44:13,974 INFO [STDOUT] A4 OK [READ-WRITE] Completed
18:44:13,974 INFO [STDOUT] A5 SEARCH UNSEEN ALL
18:44:13,993 INFO [STDOUT] * SEARCH
18:44:13,993 INFO [STDOUT] A5 OK Completed (0 msgs in 0.000 secs)
18:44:13,993 INFO [STDOUT] A6 CLOSE
18:44:14,138 INFO [STDOUT] A6 OK Completed
18:44:14,138 INFO [STDOUT] DEBUG: added an Authenticated connection -- size: 1
18:44:14,138 INFO [STDOUT] IMAP DEBUG: IMAPProtocol noop
18:44:14,138 INFO [STDOUT] A7 NOOP
18:44:14,156 INFO [STDOUT] A7 OK Completed
18:44:14,156 INFO [STDOUT] A8 LOGOUT
18:44:14,175 INFO [STDOUT] * BYE LOGOUT received
18:44:14,175 INFO [STDOUT] A8 OK Completed
18:44:14,176 INFO [STDOUT] DEBUG: IMAPStore connection dead
18:44:14,176 INFO [STDOUT] DEBUG: IMAPStore cleanup, force false
18:44:14,176 INFO [STDOUT] DEBUG: IMAPStore cleanup done
MDB implementation:
@MessageDriven(activationConfig={
@ActivationConfigProperty(propertyName="mailServer", propertyValue="127.0.0.1"),
@ActivationConfigProperty(propertyName="mailFolder", propertyValue="INBOX"),
@ActivationConfigProperty(propertyName="storeProtocol", propertyValue="imap"),
@ActivationConfigProperty(propertyName="userName", propertyValue="jbossra"),
@ActivationConfigProperty(propertyName="password", propertyValue="****"),
@ActivationConfigProperty(propertyName="debug", propertyValue="true"),
@ActivationConfigProperty(propertyName="starttls", propertyValue="false"),
@ActivationConfigProperty(propertyName="pollingInterval", propertyValue="60000")
})
@ResourceAdapter("mail-ra.rar")
public class MailBean implements MailListener {
public void onMessage(Message message) {
// Process the message
try {
System.out.println("Message received:"+message.getSubject());
} catch (MessagingException e) {
e.printStackTrace();
}
}
}
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 5 months
[JBoss JIRA] Created: (AS7-1264) Add schema references to standalone.xml, domain.xml, host.xml
by Gerry Matte (JIRA)
Add schema references to standalone.xml, domain.xml, host.xml
-------------------------------------------------------------
Key: AS7-1264
URL: https://issues.jboss.org/browse/AS7-1264
Project: Application Server 7
Issue Type: Task
Components: Domain Management
Affects Versions: 7.0.0.CR1
Reporter: Gerry Matte
Assignee: Brian Stansberry
It appears that users of Jboss 7 will be often modifying these configuration files as they fine tune their server and when they discover how to implement new features.
It seems quite surprising to me that these files do not have the schema references identified in the file header. Any good XML editor would use those references to validate changes and new entries and thereby avoid a great deal of frustration for users and those who provide support for forum issues.
I realise that if jboss validated each xml file when starting up there would be performance penalty that may be unacceptable to many users. A command-line switch could be used to either turn on xml validation (if the default were that no validation is performed) or conversely to turn off xml validation if the default state was that xml validation was on.
Personally I favor having a switch that turns off validation - to be used on production servers only.
If the schema/dtd files were published online and referenced within the configuration xml files, future changes to the schema structure would be "enforced" upon the user community as they attemted to use an out-of-date version when upgrading to a new version of Jboss 7.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 5 months
[JBoss JIRA] Created: (JBAS-9203) EJBAccessException dont contains my LoginException thrown in a custom LoginModule during login-Method
by Felix Ullrich (JIRA)
EJBAccessException dont contains my LoginException thrown in a custom LoginModule during login-Method
-----------------------------------------------------------------------------------------------------
Key: JBAS-9203
URL: https://issues.jboss.org/browse/JBAS-9203
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Security
Affects Versions: 6.0.0.Final
Reporter: Felix Ullrich
Assignee: Anil Saldhana
This problem was already mentioned here: [http://community.jboss.org/message/114379] A thrown LoginException in a custom LoginModule is not correctly wrapped into the javax.ejb.EJBAccessException on client-side. The cause of EJBAccessException is just not set - its null...
The RemoteClient-Code looks like this
try {
ejb.someMethod();
} catch (final EJBAccessException e) {
e.printStackTrace();
throw e.getCause();
}
and the Stacktrace:
javax.ejb.EJBAccessException: Invalid User
at org.jboss.ejb3.security.Ejb3AuthenticationInterceptorv2.invoke(Ejb3AuthenticationInterceptorv2.java:161)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
at org.jboss.ejb3.ENCPropagationInterceptor.invoke(ENCPropagationInterceptor.java:41)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
at org.jboss.ejb3.BlockContainerShutdownInterceptor.invoke(BlockContainerShutdownInterceptor.java:67)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
at org.jboss.ejb3.core.context.CurrentInvocationContextInterceptor.invoke(CurrentInvocationContextInterceptor.java:47)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
at org.jboss.aspects.currentinvocation.CurrentInvocationInterceptor.invoke(CurrentInvocationInterceptor.java:67)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
at org.jboss.ejb3.interceptor.EJB3TCCLInterceptor.invoke(EJB3TCCLInterceptor.java:86)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
at org.jboss.ejb3.stateful.StatefulContainer.dynamicInvoke(StatefulContainer.java:603)
at org.jboss.ejb3.session.InvokableContextClassProxyHack._dynamicInvoke(InvokableContextClassProxyHack.java:53)
at org.jboss.aop.Dispatcher.invoke(Dispatcher.java:91)
at org.jboss.aspects.remoting.AOPRemotingInvocationHandler.invoke(AOPRemotingInvocationHandler.java:82)
at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:898)
at org.jboss.remoting.transport.socket.ServerThread.completeInvocation(ServerThread.java:791)
at org.jboss.remoting.transport.socket.ServerThread.processInvocation(ServerThread.java:744)
at org.jboss.remoting.transport.socket.ServerThread.dorun(ServerThread.java:548)
at org.jboss.remoting.transport.socket.ServerThread.run(ServerThread.java:234)
at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:216)
at org.jboss.remoting.Client.invoke(Client.java:1961)
at org.jboss.remoting.Client.invoke(Client.java:804)
at org.jboss.aspects.remoting.InvokeRemoteInterceptor.invoke(InvokeRemoteInterceptor.java:60)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
at org.jboss.aspects.tx.ClientTxPropagationInterceptor.invoke(ClientTxPropagationInterceptor.java:61)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
at org.jboss.ejb3.security.client.SecurityClientInterceptor.invoke(SecurityClientInterceptor.java:65)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
at org.jboss.ejb3.remoting.IsLocalInterceptor.invoke(IsLocalInterceptor.java:77)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
at org.jboss.ejb3.async.impl.interceptor.AsynchronousClientInterceptor.invoke(AsynchronousClientInterceptor.java:143)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
at org.jboss.aspects.remoting.PojiProxy.invoke(PojiProxy.java:62)
at $Proxy8.invoke(Unknown Source)
at org.jboss.ejb3.proxy.impl.handler.session.SessionProxyInvocationHandlerBase.invoke(SessionProxyInvocationHandlerBase.java:185)
at $Proxy7.findAll(Unknown Source)
at RemoteClient.main(RemoteClient.java:22)
at org.jboss.aspects.remoting.InvokeRemoteInterceptor.invoke(InvokeRemoteInterceptor.java:72)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
at org.jboss.aspects.tx.ClientTxPropagationInterceptor.invoke(ClientTxPropagationInterceptor.java:61)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
at org.jboss.ejb3.security.client.SecurityClientInterceptor.invoke(SecurityClientInterceptor.java:65)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
at org.jboss.ejb3.remoting.IsLocalInterceptor.invoke(IsLocalInterceptor.java:77)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
at org.jboss.ejb3.async.impl.interceptor.AsynchronousClientInterceptor.invoke(AsynchronousClientInterceptor.java:143)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
at org.jboss.aspects.remoting.PojiProxy.invoke(PojiProxy.java:62)
at $Proxy8.invoke(Unknown Source)
at org.jboss.ejb3.proxy.impl.handler.session.SessionProxyInvocationHandlerBase.invoke(SessionProxyInvocationHandlerBase.java:185)
at $Proxy7.findAll(Unknown Source)
at RemoteClient.main(RemoteClient.java:22)
Exception in thread "main" java.lang.NullPointerException
at RemoteClient.main(RemoteClient.java:25)
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 5 months