[JBoss Tools] - Re: JBoss AS7 freezes at startup when launching in debug mode from Eclipse.
by Jim Brownfield
Jim Brownfield [https://community.jboss.org/people/jbrow] created the discussion
"Re: JBoss AS7 freezes at startup when launching in debug mode from Eclipse."
To view the discussion, visit: https://community.jboss.org/message/720352#720352
--------------------------------------------------------------
I have the same problem, but the "server started" line actually gets printed, but the server never gets to the started state. There is, apparently, a deadlock between two threads:
> 2012-02-28 13:03:32
> Full thread dump Java HotSpot(TM) 64-Bit Server VM (20.4-b02-402 mixed mode):
>
> [snip...]
>
>
>
> Found one Java-level deadlock:
> =============================
> "Remoting "jim-brownfields-macbook-pro:MANAGEMENT" task-1":
> waiting to lock monitor 7fd5238be3f0 (object 7d56970f8, a org.jboss.remoting3.remote.InboundMessage),
> which is held by "Remoting "jim-brownfields-macbook-pro:MANAGEMENT" read-1"
> "Remoting "jim-brownfields-macbook-pro:MANAGEMENT" read-1":
> waiting to lock monitor 7fd52a103e90 (object 7d5697118, a org.xnio.streams.BufferPipeInputStream),
> which is held by "Remoting "jim-brownfields-macbook-pro:MANAGEMENT" task-1"
>
>
> Java stack information for the threads listed above:
> ===================================================
> "Remoting "jim-brownfields-macbook-pro:MANAGEMENT" task-1":
> at org.jboss.remoting3.remote.InboundMessage.openInboundWindow(InboundMessage.java:128)
> - waiting to lock <7d56970f8> (a org.jboss.remoting3.remote.InboundMessage)
> at org.jboss.remoting3.remote.InboundMessage$2.acknowledge(InboundMessage.java:63)
> at org.xnio.streams.BufferPipeInputStream.read(BufferPipeInputStream.java:195)
> - locked <7d5697118> (a org.xnio.streams.BufferPipeInputStream)
> at org.jboss.remoting3.remote.InboundMessage$3.read(InboundMessage.java:86)
> at java.io.FilterInputStream.read(FilterInputStream.java:116)
> at java.io.FilterInputStream.read(FilterInputStream.java:90)
> at org.jboss.marshalling.SimpleDataInput.readByte(SimpleDataInput.java:213)
> at org.jboss.as.protocol.mgmt.ProtocolUtils.expectHeader(ProtocolUtils.java:84)
> at org.jboss.as.protocol.mgmt.ManagementProtocolHeader.parse(ManagementProtocolHeader.java:110)
> at org.jboss.as.protocol.mgmt.ManagementChannelReceiver.handleMessage(ManagementChannelReceiver.java:67)
> at org.jboss.remoting3.remote.RemoteConnectionChannel$5.run(RemoteConnectionChannel.java:435)
> at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
> at java.lang.Thread.run(Thread.java:680)
> "Remoting "jim-brownfields-macbook-pro:MANAGEMENT" read-1":
> at org.xnio.streams.BufferPipeInputStream.pushEof(BufferPipeInputStream.java:112)
> - waiting to lock <7d5697118> (a org.xnio.streams.BufferPipeInputStream)
> at org.jboss.remoting3.remote.InboundMessage.cancel(InboundMessage.java:186)
> - locked <7d56970f8> (a org.jboss.remoting3.remote.InboundMessage)
> at org.jboss.remoting3.remote.RemoteConnectionChannel.handleMessageData(RemoteConnectionChannel.java:424)
> at org.jboss.remoting3.remote.RemoteReadListener.handleEvent(RemoteReadListener.java:234)
> at org.jboss.remoting3.remote.RemoteReadListener.handleEvent(RemoteReadListener.java:45)
> at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:72)
> at org.xnio.channels.TranslatingSuspendableChannel.handleReadable(TranslatingSuspendableChannel.java:189)
> at org.xnio.channels.TranslatingSuspendableChannel$1.handleEvent(TranslatingSuspendableChannel.java:103)
> at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:72)
> at org.xnio.nio.NioHandle.run(NioHandle.java:90)
> at org.xnio.nio.WorkerThread.run(WorkerThread.java:184)
>
>
> Found 1 deadlock.
>
The full thread dump is attached.
--------------------------------------------------------------
Reply to this message by going to Community
[https://community.jboss.org/message/720352#720352]
Start a new discussion in JBoss Tools at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]
14 years, 1 month
[jBPM] - jBPM 5.2 Pipelining
by gboro54
gboro54 [https://community.jboss.org/people/gboro54] created the discussion
"jBPM 5.2 Pipelining"
To view the discussion, visit: https://community.jboss.org/message/720187#720187
--------------------------------------------------------------
This may span both rules authoring and the business process but I figured I would start here. We are using jBPM 5.2 to orchestration rule-execution and business logic. The issue we are running into now is as follows: The first 50-60% of the rules can be arbitraly fired on messages in any order(i.e if you have message 1, message 2 and message 3 in working memory the order in which the rules consequencesoccur does not matter). However the last 40%-50% order does matter(i.e message 1 consequences have to occur before number 2,etc.). For the purpose of speed we are looking for a way to execute the 1st n number of rule-flow groups/logic in a multithreaded way and the 2nd number single threaded in order. Is there anyway to have jBPM handle this orchestration. I have thought about having two seperate processes coordinated by some logic outside of the engine. I have also thought about doing something with a sub-process but I am unclear about how the session works with the sub-process(i.e if I start a subprocess does it have it's own working memory or does it utilize the same one as the parent)... Any light on this subject would be greatly appricated.
--------------------------------------------------------------
Reply to this message by going to Community
[https://community.jboss.org/message/720187#720187]
Start a new discussion in jBPM at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]
14 years, 1 month
[JBoss Tools] - JPA validation fails
by Jesper Skov
Jesper Skov [https://community.jboss.org/people/jskovjyskebankdk] created the discussion
"JPA validation fails"
To view the discussion, visit: https://community.jboss.org/message/720006#720006
--------------------------------------------------------------
Hi,
I just closed an issue I created against Dali: https://bugs.eclipse.org/bugs/show_bug.cgi?id=372478 https://bugs.eclipse.org/bugs/show_bug.cgi?id=372478 (I included the text below)
It appears that the JPA validation error (Column "attributes" cannot be found on table...) we get is due to a problem in JBoss Tools, Hibernate.
I wonder if we need to "do something" to make the validation pass, or it is indeed a bug. We can disable the validation as a workaround, but would like it working, obviously.
The reason I ask, is that it seems such an obvious problem, and I can't find anything currently open (or closed) in Jira to explain it.
We see it in more than one class. Maybe it's just a problem with the coding style here :^0
On the other hand, switching the JPA platform to Generic fixes the problem, so maybe not.
I just tried the JBoss Tools nightly build from yesterday (on 3.7sr2) and could still reproduce.
Is it something I should file a Jira issue for?
Thx,
Jesper
------ from the closed Eclipse issue -------
Build Identifier: Build id: 20120216-1857
We see a false error from the validation rule: Database/Column/Column cannot be
resolved.
The class with the validation error is this:
@Entity
@Table(name = "PasswordResourceAuditLog", uniqueConstraints =
@UniqueConstraint(columnNames = { "timestamp" }))
public class PasswordResourceAuditLogEntry extends UUIDEntity implements
LogEntry, Serializable {
@Column(length = 50)
private String username;
private String dataSourceName;
@Temporal(TemporalType.TIMESTAMP)
private Date timestamp;
@OneToOne(fetch=FetchType.EAGER)
private PasswordAttributes attributes;
...
The field attributes gets a validation error:
Column "attributes" cannot be resolved on table "PASSWORDRESOURCEAUDITLOG"
The class PasswordAttributes looks like this:
@Inheritance(strategy = InheritanceType.TABLE_PER_CLASS)
@Entity
abstract public class PasswordAttributes extends UUIDEntity {
public abstract PasswordAttributes copy();
public abstract PasswordType getType();
public void setType(PasswordType type){
//dummy method due to EL
}
}
and in turn:
@MappedSuperclass
public class UUIDEntity implements Serializable {
@Id @GeneratedValue(generator="system-uuid")
@GenericGenerator(name="system-uuid",strategy = "uuid")
@Column(length=32)
@Size(max=32, min=32)
protected String id;
@SuppressWarnings("unused")
@Version
private Long version;
public String getId() {
return id;
}
}
Looking in the database (tables created by Hibernate, no custom configuration
as far as I know), the column is actually called ATTRIBUTES_ID.
We would expect the validator to look for this, not a column named ATTRIBUTES.
--------------------------------------------------------------
Reply to this message by going to Community
[https://community.jboss.org/message/720006#720006]
Start a new discussion in JBoss Tools at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]
14 years, 1 month